(Connection Standard between SSP and SCP for Local Number Portability)

Transcription

1 TTA Standard Enacted on : 19 Dec TTAS.KO /R2 Revised on : 11 Dec Revised on : 23 Dec (Connection Standard between SSP and SCP for Local Number Portability) Telecommunications Technology Association

2 TTA Standard Enacted on : 19 Dec TTAS.KO /R2 Revised on : 11 Dec Revised on : 23 Dec (Connection Standard between SSP and SCP for Local Number Portability) Telecommunications Technology Association

3 Preface 1. Objective The Objective of this Specification is redefinition of "Connection standard between SSP and SCP" for Number Portability system in which QoR is used. This standard is based on the No.7 signal network and Intelligent Network. This Specification redefined only the part which should be changed or added according to the Number Portability system which is used in Korea. 2. Normative standards and recommendations 2.1 International Standards ITU-T Recommendations, Q.701 ~ Q.708, MTP Specifications of SS7", ITU-T Recommendations, Q.711 ~ Q.716, SCCP Specifications of SS7", ITU-T Recommendations, Q.761 ~ Q.764, ISUP Specifications of SS7", ITU-T Recommendations(Draft), Q.769.1, SS7 ISUP Enhancements for the Support of Number Portability", COM11-R162, ITU-T Recommendations, Q.1200 series, INAP Specifications of SS7", ITU-T Recommendations, Q.699, Interworking between ISDN Access and Non-ISDN Access over ISUP", ITU-T Recommendations, Q.730, ISDN User Part Supplementary Services", 1999 ITU-T Recommendations, Q.850, Use of cause and location in the digital subscriber Signaling System No.1 and Signaling System No.7 ISDN user part" ITU-T Recommendations, Q.1600, Interaction between ISUP and INAP" ANSI T1, Technical Requirements for Number Portability - Database and Global Title Translations", T1S1.6(Number Portability), i

4 ANSI T1, Baseline Working Documents for Switching and Signaling", T1S1.6/98-001, TIA/EIA, IS-41D, Cellular Radiotelecommunications Intersystem Operations", TIA/EIA, IS-756.A, IS-41D Enhancements for Wireless Number Portability Phase- Ⅱ", GPP 3G TS CAMEL Phase3.CAP Specification 3GPP 3G TS CAMEL Phase3 Stage2 3GPP 3G TS CAMEL Phase1 Service Description 3GPP 3G TS Support of Mobile Number Portability(MNP); Service description stage1 3GPP 3G TS Support of Mobile Number Portability(MNP); Technical Realization ; stage2 2.2 Domestic Standards KICS.IT-Q711, Standard for Signaling System No.7 (Signaling Connection Control Part); Services Overview", KICS.IT-Q712, Standard for Signaling System No.7 (Signaling Connection Control Part); Definition of Terms, KICS.IT-Q713, Standard for Signaling System No.7 (Signaling Connection Control Part); Formats and Codes, KICS.IT-Q714, Standard for Signaling System No.7 (Signaling Connection Control Part); Signaling Procedures, KICS.IT-Q761, Standard for Signaling System No.7 (Signaling Connection Control Part); Basic Functions fo ISDN User Part, KICS.IT-Q762, Standard for Signaling System No.7 (Signaling Connection Control Part); Definition of Signaling Message and Signaling Information KICS.IT-Q763, Standard for Signaling System No.7 (Signaling Connection Control Part); Formats and Codes, KICS.IT-Q764, Standard for Signaling System No.7 (Signaling Connection Control Part); Signaling Procedure, ii

5 KICS.IT-Q771, Standard for Signaling System No.7 (Transaction Capability Application Part); Functional Description, KICS.IT-Q772, Standard for Signaling System No.7 (Transaction Capability Application Part); Information Element Definitions, KICS.IT-Q773, Standard for Signaling System No.7 (Transaction Capability Application Part); Formats and Encoding, KICS.IT-Q774, Standard for Signaling System No.7 (Transaction Capability Application Part); Procedures, KICS.KO Standard of No.7 Signaling System (FP-ASE), TTAE.3G IMT2000 3GPP - CAMEL Phase Stage 3 TTAE.3G IMT2000 3GPP - CAMEL Phase 3 - Stage2 TTAE.3G IMT2000 3GPP - CAMEL Stage 1 TTAE.3G IMT2000 3GPP - Support of MNP Stage 1 TTAE.3G IMT2000 3GPP - Support of MNP Stage Others 3. The Comparison of international standards 3.1 The relationship of international Standards This Specification is conceptually related of the ITU-T Recommendation Q.701~ 708,Q.711~716, Q.761~Q.766, Q.771~Q.774, Q.1200, Q.850. It is changed and added according to the QoR method which will e forced in Korea. 3.2 Additional requirement to international standard None iii

6 3.3 Differences between Ver1 and Ver2 The first edition The second edition Remark The name of (1) Connection standard between SSP (1) Connection standard standard is and SCP for Local Number Portability between SSP and SCP changed for Number Portability (2) modify the message format such as CPDN, CDN and its range of application and contents (3) modify WIN(MAP) protocol Change clause (4)change freephone (080) to freephone (5) add continue operation to Change Chapter 7 All over this Standard Add new parameter 4. Intellectual property rights Reference None 5. Requirements for conformance and Certification None 6. Revised Contents - CPDN, CDN message - WIN(MAP) Protocol - Modify the terms of the free phone service (080) to the free phone service - Add the continue operation in iv

7 7. History Edition Issue Date Contents The first edition Established The second edition Revised The third edition Revised v

8 vi

9 CONTENTS 1. OBJECTIVE 1 2. SCOPE AND FIELD OF APPLICATION SCOPE OF APPLICATION RESTRICTIONS 3 3. TERMINOLOGIES 4 4. REQUIREMENTS OF LOW LAYER PROTOCOLS REQUIREMENTS OF TCAP PROTOCOL REQUIREMENTS OF SCCP PROTOCOL UIREMENTS OF MTP PROTOCOL 9 5. INAP ENHANCEMENTS FOR NUMBER PORTABILITY 11 vii

10 5.1 PROCEDURE OF APPLICATION PROTOCOL OPERATIONS PARAMETER AND CODES USER GUIDELINES OF INAP FOR NUMBER PORTABILITY GUIDELINE FOR NP APPLICATION Guideline for the application of free phone service WIN(MAP) ENHANCEMENTS FOR NUMBER PORTABILITY GENERALS OPERATION AND ERROR PARAMETER ENHANCEMENTS SIGNALING PROCEDURE REQUIREMENTS OF LOWER LAYER PROTOCOL CAP ENHANCEMENTS FOR NUMBER PORTABILITY 30 viii

11 8.1 GENERAL OPERATION PROCEDURE PARAMETERS REQUIREMENTS OF LOWER LAYER PROTOCOL FP-ASE ENHANCEMENTS FOR NUMBER PORTABILITY GENERAL OPERATION ENHANCEMENTS PARAMETER ENHANCEMENTS SIGNALING PROCEDURE ENHANCEMENTS 38 APPENDIX. ABBREVIATIONS 39 ix

12 Connection standard between SSP and SCP for local number portability 1. Object This standard defines the protocols required between SSP and SCP systems by QoR method to offer number portability of local call and freephone service to the national electric telecommunication networks. This standard defines additional requirements or changes required in existing national protocol standards in order to provide necessary signaling capability to the related systems according to the number portability network functional standards. 2. Scope and filed of application It is fundamental to apply INAP (Q.1218) protocol or appropriate national standard recommended by ITU-T for the signaling connection protocol between SSP and SCP systems to provide number portability. However, applying WIN (MAP) or CAP protocol instead of INAP protocol is allowed in MSC which has applied WIN (MAP). 2.1 Scope of application This standard restricts the purpose of providing relative number portability to the signaling connect standard that is applied between SSP and SCP systems. Picture 1 defines functional model structure and interface of INAP protocol considering appropriate number portability. SSP system subject to number portability basically applies NPCF and NPDF function. Signal connection (D') between CCPE and NPCE functions is complementally defined by existing signal connection (D) between SSF and SCF functions as a basis. Signal connection (F') between NPCF and NPDF functions applies existing signal connection (F) between SCF and SDF functions as it is. 1

13 But, since functions of NPCF and NPDF are assumed to be consolidated in one SCP system, signaling connection between them is not separately defined in this standard. Signal connection (M') between CCF and CCPE functions is complementally defined by existing signal connection (M) between CCF and SSF functions as a basis. Rules regarding this will be defined in a separate standard This standard additionally defines the parts that ought to be supplemented or changed by this number portability among signal connection (D) applied between SSF and SCF functions that are object to provide freephone service which is an object of relative number portability Management connection standard related with management system such as SMS and M- is defined as a separate standard. Signaling connection included in the application range of this document Signaling connection excluded in the application range of this document Signaling connection excluded in the application range of this document but needs to be considered when interworking service. Signaling connection excluded in the application range of this document (Picture 1) Functional model structure and interface of INAP protocol 2

14 2.2 Preconditions Number portability which is the subject of this standard is restricted to service provider portability of local call and freephone service Number portability method which is also the subject of this standard follows QoR (Query of Release) method prescribed by related Network Functional Standards" that have been composed based on NP CS-1 of ITU-T Although SSP and SCP systems that provide number portability are included in the same service provider network, the signaling connection is in principle to follow this standard s criterion This number portability application does not involve IP system. Therefore, SRF function and interface are not considered NPDF function is assumed to be integrated with NPCF function in a same SCP system. Therefore, a signaling connection between these functions is decided within the provider This standard describes operation and parameter necessary for embodying relative number portability, and definition and process of appropriate operation that are identical to ITU-T Q.1218 INAP recommendation will not be described in this standard FSM condition of CCPE (SSF) and NPCE (SCF) functions will be described as the condition required in operation process used by application entity of number portability Besides the operations defined in this standard, non-call related management operation (ex. call gapping) can be added depending on provider's needs. 3

15 3. Terminology 3.1. NP (Number Portability) : Refers to all capabilities of service provider portability, location portability and service portability SPP (Service Provider Portability) : Network capability which enables subscribers to retain their existing telephone number when changing local telephone providers Location portability : Network capability which enables users to retain existing telephone number when their geographical locations change Service portability : Network capability which enables users to retain existing telephone numbers when service type changes Service provider : The provider who offers telecommunication service to end users after being authorized by government or authorities concerned End user : General customers who use telecommunication services. Based on position of their service usages, they can be divided into subscribers who use one or more telephone numbers assigned by a certain network provider after signing up a subscription, and users who use telephone services regardless of a subscription and phone number assignment Area code : Numbers which classify areas according to national numbering plans Ported number : Telephone number that a subscriber has changed a subscription from the existing switch (or DB system), which has provided the service to the subscriber so far, to another switch (or DB system). Types of number portability may differ depending on an owning provider, a location and a service function of two switches (or DB system). 3.9 Initiating switch : Switch which starts routing to a destination switch for a given call by obtaining routing information of the destination switch for call connection to the ported number. 4

16 3.10. Donor switch : Destination switch which processes routing to complete a call without consideration of number portability. Or, a switch which has been received destination service until a subscriber has been ported out Recipient switch : Switch that accepts present incoming call subscribers and provides a service to them after the number porting Transit switch : Switch which passes by two switches when a call has been progressed between an originating switch and a destination switch. It requires capability of processing routing information for number portability Gateway switch : Gate switch which connects different service provider networks. Several cases such as real IGS, Toll, gateway MSC, etc., can be appeared depending on connection system between networks Donor service network : Intelligent network which has provided the subscribers with relevant services without consideration of number portability. Or, service provider network which has provided with services right before an intelligent service subscriber ports out Recipient service network : Service provider network that accepts Intelligent Network subscribers and provides a service to them after the subscription being changed NPDB : Database which contains information required to provide capability of number portability FPDB : Database which contains information required to provide freephone service NP query Query that has been tried from a query switch to a number portability database in order to acquire routing information of subscribers who have ported out Free phone query : Query which SSP tries to perform into SCP in order to acquire actual routing information on subscribers of freephone service. 5

17 3.20. NP information : Information required to identify recipient switch. It includes network routing number, service provider identifier and location of ported number Routing number : Identification number of recipient switch in network, which is used in routing from destination switch to originating sides Non-circuit related message : Message for exchanging signal information between systems using TCAP/SCCP protocol without direct relation to setting up or restoration of a circuit. It is used in control of ISDN supplementary service or intelligent network service BER : It is non-compelled, and one of correction methods for signal link error which uses positive/negative confirmation and re-sending. It is applied to a ground link whose delay of single direction electric wave is less than 15 ms PCR : It is non-compelled, and one of correction methods for signal link error which uses positive confirmation and circular re-sending. It is applied to intercontinental satellite link whose delay of single direction electric wave is more than 15 ms NI : Field that is commonly included in MTP message. It supports decoding method for OPC and DPC and Service Indication SEP : It refers to signaling point that finally sends or receives a message incurred by No.7 MTP users, and can be classified as an originating point or a destination point. The SP which is not usual signaling end-point is STP Signaling connection : Virtual circuit where SCCP is formed between its users who are located at different signaling points Connectless service : Network layer service which conveys user data without setting up signaling connection between SCCP QoS : Refers to all elements related in network layer services such as protocol class that will be applied to signaling connection, message indication assurance, message return selection, and window size for message flow control. This may be an object of mutual negotiation when high layers request signaling connection. 6

18 3.30. Global title : Numbering information which is promised between application layer function parts like the telephone number in telephone network NoA : Field included in address-related parameter such as received party number and called party number. It is also defined as a indicator which determines characteristics or types of relative numbers Prearranged end : Method which is promised in advance that related users will partially finish the transaction without giving shut-down information in the given transaction Operation : TCAP users at originating part indicate TCAP users at destination part to execute given action, and this operation is defined as operation code, class, timer, indicating parameter, relative error code, available linked operation, etc Operation class : Class that orders available response to standby according to the result of success or failure for the given operation instruction Linked operation : The other operation being returned as a response to an operation indication within given transaction ASE : Unit service element that can be commonly used within several application entities. It consists of a set of several actions Application context : Classification of application layer suggested by dialogue initiator and dialogue responder on a given dialogue. Single application context clearly defines ASE set, related option and other necessary information that are needed in interaction between application entities. 7

19 4. Requirements of low layer protocols Low No.7 protocol, that is, special requirements for TCAP, SCCP and MTP protocol are defined in order to apply this INAP protocol Requirements of TCAP protocol TCAP protocol follows national standards or ITU-T recommendation corresponding with ITU-T TCAP Blue version(1933)or higher version. There are no particulars to be added or changed for providing relative number portability TCAP protocol has several options. At the point of sub-provider of this INAP protocol, the following items are premised in order to clarify application of relative TCAP protocol function. Do not apply enhanced dialogue control facilities and its related dialogue portion within TCAP message for application context negotiation. Do not apply segmented result function since segmented result components for this number portability and its related operation instruction are not long enough to require segmentation. That is, RR-NL components and its related TC-RESULT-NL primitive will not be applied. Selection of basic end and prearranged end when finishing a dialogue will be applied same as the relative operation defined in INAP standard. There are no special requirements regarding QoS, originating or destination side addressing and signaling network condition management. That is, information related to them will be transferred between INAP and SCCP as it is Requirements of SCCP protocol SCCP protocol follows national stadard or ITU-T recommendation corresponding with ITU SCCP Blue version(1933) or higher version. There are no particulars to be added or changed for providing relative number portability. 8

20 SCCP protocol between SSP and SCP systems for this number portability provides connectless signaling connection service. SCCP protocol class uses 0 (basic connectless class) in principle, however 1 (sequence control connectless class) can be used depending on the case. Use basic messages (UDT and UDTS) and do not use extended messages (XUDT XUDTS, LUDT and LUDTS). There are no additional requirements for QoS of connectless service SCCP protocol must support freephone application entities that are subject of number portability and number portability entities. When transacting between SSP and SCP, the addressing do not use GT. Instead, signaling point code (SPC) and sub-system number (SSN) are used in principle. SSN for number portability application entities is not separately defined. INAP SSN (0xF1) will be applied as a principle Performance of SCCP protocol should satisfy ITU-T Recommendation Q.716 or corresponding national standard. That is, the existing standard related to SCCP performance is not affected even if number portability is added Requirements of MTP protocol ISCCP protocol follows national stadard or ITU-T recommendation corresponding with ITU SCCP Blue version(1933) or higher version. There are no particulars to be added or changed for providing relative number portability MTP protocol has several options. The following items are necessary to be premised in order to clarify application of relative MTP protocol function. 9

21 MTP protocol of SSP and SCP systems only have to provide function as signaling and point(sep). That is, signaling transfer point(stp) traditional function and its related message will not be applied as long as SSP and SCP systems provide special STP function. Signaling link error correction method only applies BEC(Basic Error Correction method and does not apply PCR(Preventive Cyclic Retransmission) method since signaling link between SSP and SCP only applies a ground link and does not apply a satellite link. Signaling link management process makes it principle to apply the management process and does not apply the management process and message assuming automatic allocation of terminal and signaling data link. Signaling congestion level only applies single congestion level. Therefore, function and message related to multiple congestion level are not applied MTP message label is applied as follows. Signaling Point Code (SPC) applies 14 bit. Especially, signaling point code applies as specified in ITU-T Recommendation Q.708 or corresponding national standard when transferring messages between service providers. Network Indicator (NI) of sub-service portion is indicated as national network (0b10) and standby bit is filled with 0b Performance of MTP protocol should satisfy ITU-T Recommendation Q.706 or corresponding national standard. That is, the existing standard related to SCCP performance is not affected even if number portability is added. 10

22 5. INAP enhancements for number portability 5.1 Procedure of application protocol Producer of CCPF application entity This corresponds to SSF application entity Producer of NPCF application entity This corresponds to SCF application entity Producer of NPDF application entity This corresponds to SDF application entity Operations General Operation of initial DP of INAP, connection, and release call are basically used as SSP SCP signaling connection for number portability application Number portability application does not require signaling connection between SSP/SCP IP systems, and SDF function entity is assumed to be combined within SCP system Besides operations defined in this standard, non-call related management operation (ex. call gapping) can be added depending on providers needs Initial DP operation 11

23 General This operation is applied for number portability query and indicated from CCPF to NPCF. Called party number parameter should be included in principle and this parameter is used in inquiry of number portability database. The rest of the parameters are applied as an option parameter based on criterion of INAP standard. This operation is able to apply for freephone service query and indicated from SSF to SCF. Originating and called party number parameters should be included in principle for freephone service and these parameters are used in freephone database inquiry. The rest of the parameters are applied as an option parameter based on criterion of INAP standard Definition of operation 12

24 Initial DP operation Direction : CCPF (SSF) NPCF (SCF) Timer : T idp Class : 2 Code value : localvalue 0 Initial DP parameter (type :SEQUENCE) Requirement/ Remark Service key Input digit Called party number Originating number Originating service group number Originating class Originating sub-address Call gapping sensing IPSSP usability IP capability Location number Other call information Initial called party number Service profile identifier Terminal type Trigger type High layer compatibility Service interaction indicator Additional originating number Forwarding call indicator Bearer capability BCSM case type Call diverting originating number Call diverting information Extension Requirements Required for NP application entity and FP application entity Required for FP application entity 13

25 Error Subscriber record nonexistence Parameter nonexistence Parameter error System breakdown Operation rejection Unexpected component sequence Unexpected data value Unexpected parameter Abstract context (ASN.1) notation Initial DP ::=OPERATION ARGUMENT Initial DP parameter ERRORS { Subscriber record nonexistence, Parameter nonexistence, Parameter error, System breakdown, Operation rejection, Unexpected component sequence, Unexpected data value, Unexpected parameter } 14

26 Initial DP parameter ::= SEQUENCE { Service key [0] Input digit [1] Called party number [2] Originating number [3] Originating service group number [4] Originating class [5] Originating sub-address [6] Call gapping sensing [7] ipssp capability [8] ip usability [9] Location number [10] Other call information [11] Initial called party number [12] Service profile identifier [13] Terminal type [14] Extension [15] Trigger type High layer compatibility Service interaction indicator Additional originating number Forwarding call indicator Bearer capability BCSM case type Call diverting originating number Call diverting information } [16] [23] [24] [25] [26] [27] [28] [29] [30] Service key Called party number Called party number Originating number Originating service group number Originating class Originating sub-address Call gapping sensing IPSSP capability IP usability Location number Other call information Initial called party number Service profile identifier Terminal type SEQUENCE SIZE (1..extention number) OF extension field Trigger type High layer compatibility Service interaction indicator Additional originating number Forwarding call indicator Bearer capability BCSM case type Call diverting originating number, call diverting information OPTIONAL Producer of application entity Producer of CCPF and NPCF processes are applied based on existing SSF and SCF processes respectively Connect operation General This operation is applied as a normal sequence operation for initial DP operation, and destination routing address parameter is included in principle. This parameter includes called party number and the number includes addresses for routing to destination side for CCPE (SSF). The rest of parameters are applied as option parameters according to INAP standard criterion. 15

27 In case of a called party number indicated on initial DP operation in number portability application has been ported, a destination parameter of this operation uses it for transferring the address of final destination switch or identifying address of final destination network that the ported number has been serviced to. This operation is also used as normal response for freephone service query. In this case, called party number includes actual routing number for destination pay number Definition of operation Connect operation Direction : NPCF (SCF) CCPF (SSF) Timer : T con Class : 2 Code value : localvalue 20 Connection parameter (type:sequence) Destination routing address Page type Correlation number Delete and attach Forward direction condition ISDN access-related information Initial called party number Routing list SCF number Ported class indication Service provider Service interaction indicator Originating number Originating class Call diverting originating number Call diverting information Extension Error Parameter nonexistence Parameter error System breakdown Operation rejection Unexpected component sequence Unexpected data value Unexpected parameter Requirements / Requirements Remark Requirements for NP application entity and FP application entity 16

28 Abstract context (ASN.1) notation Connection ::= OPERACTION ARGUMENT connection parameter ERRORS { Parameter nonexistence, Parameter error, System breakdown, Operation rejection, Unexpected component sequence, Unexpected data value, Unexpected parameter } connection parameter ::=SEQUENCE { Destination routing address [0] Page type [1] Correlation number [2] Delete and attach [3] Forward direction condition ISDN access-related information Initial called party number Route list SCF number Ported class indication Extension Service provider Service interaction indicator Originating number Originating class Call diverting originating number Call diverting information } [4] [5] [6] [7] [8] [9] [10] [11] [26] [27] [28] [29] [30] Destination routing address Page type Correlation number Delete and attach Forward direction condition ISDN access-related information Initial called party number Route list SCF number Ported class indication SEQUENCE SIZE (1..extension number) OF extension field Service provider Service interaction indicator Originating number Originating class Call diverting originating number Call diverting information OPTIONAL Producer of application entity CCPF and NPCF processes comply with the existing SSF and SCF processes respectively Release call operation General 17

29 This operation is applied for letting CCPE give up additional number portability query trials and release relevant calls when termination of subscription is confirmed after the called party number indicated on initial DP operation in number portability application has been ported. In this case, cause parameters of cause values and diagnosis fields are indicated as "ported number" and "disconnected ported number" respectively. This operation is also used for the response to a freephone service query. That is, if relevant freephone number has been ported to other service provider, the cause value of the cause parameter and the diagnosis field are indicated as "ported number," and "ported between networks (service provider portability)" respectively, and applied to trials of number portability query from SSP Definition of operation Release call operation Direction : NPCF (SCF) CCPE (SSF) Timer : T rc Class : 4 Code value : local Value 22 Release call parameter Required/ Remark Cause Required Required for NP application entity and FP application entity Abstract context (ASN.1) notation Release call ::=OPERATION ARGUMENT Release call parameter Release call parameter ::= cause Producer of application entity process CCPF and NPCF processes are applied based on existing SSF and SCF processes respectively. But, in case that CCPF receives release call operation that is indicated with ported number cause value and disconnected ported number" diagnosis value, it will not try anymore number portability query and will immediately try release call. That is, CCPF does not send IAM message to 18

30 destination switch, but it sends REL message to originating switch side. In case of called party number application, if SSF receives a release call operation that is indicated with ported number : cause value and ported between networks (service provider portability), it lets CCPE process number portability without trying release call Parameter and codes Service key It is a parameter for INAP to select relevant service logic. In order to distinguish number portability logic in an existing service key value, the key value should be additionally defined Definition and structure of parameter Service key ::= Integer Service key value Value 0x999 Meaning Number portability application logic Called party number (CdPN) It represents a number on destination side. Encoding nature of address indicator among called party number parameter fields has been added because of number portability. This should be identically applied with ISUP protocol standard Definition and structure of parameter Called party number :: = OCTET STRING (SIZE (minimum called party number length..maximum called party number length)) 19

31 Odd/Even Nature of address indicator 2 INN Number plan indicator Standby 3 Second address signal First address signal ㆍㆍ n Octet alignment portion Last address signal Definition of field and encoding Nature of address indicator Meaning ~ ~ Standby Subscriber number (for domestic) Unidentified (for domestic) Domestic (specific) number International number Network specific number (for domestic) RN (for domestic) of domestic (specific) number format standby standby } } standby } } } Reserved for domestic } standby Internal Network Number indicator (INN) : This is not used. That is, it is encoded as 0. The rest fields follow existing encoding standard Destination routing address This indicates a list of called party numbers Definition and structure 1 of parameter 20

32 Destination routing address ::= SEQUENCE SIZE (3) OF called party number (Refer to Section for called party number parameter definition and structure.) Definition of field and encoding (Refer to Section for called party number parameter definition and structure.) Cause Release call operation represents the cause. ITU-T Recommendation Q.850 standard will be applied and it must be applied same as ISUP protocol standard Definition of parameter and encoding 2 Cause ::= OCTET STRING (SIZE (minimum cause length..maximum cause length)) Encoding standard 0 Location 2 1 Cause value 3 : : 3n Diagnosis Field definition and encoding Cause value : The following are added to the prescribed code in ITU-T Recommendation Q Size are available for maximum of 3, but one called party number will be included this number portability. 2 Diagnosis field can be omitted depending on cause value. If cause value is "ported number," 1 octet of diagnosis field will given. 21

33 Meaning 000 i110 Ported number Diagnostics : When cause value is "ported number", it can include diagnostic values of 1 octet as follows. If diagnostic field is skipped, the diagnostic value is regarded as "no-indication" Meaning No-indication Porting within network (location portability) Porting between networks (provider portability) Porting between networks (intelligent network porting) ~~~~~~~~ (standby : by portability type) The rest of fields follows the existing rules of coding. 22

34 6. User guidelines of INAP for number portability 6.1 Guideline for NP application This section provides a guideline for number portability application process of SSP and SCP systems, and a basis for INAP protocol supplementary standard of a system Number portability application query process Initial DP operation will be applied for number portability query from SSP system. When multiple application logics exist as INAP users, service key parameter should included, and the key should be indicated as a value which identifies number portability application logic. Called party number parameter should be included if necessary. Other optional parameters, originating number for example, can be included if necessary Initial DP operation is class 2 and operation error is processed as follows. If required parameter or optional parameter needed for number portability application process haven t been received, return error value which indicates parameter nonexistence. When digits of called party number has been inputted with numbers that are unavailable to process, return error value that indicates parameter error. If a parameter has unexpected value, return error value that indicates unexpected data value. When a called party number requested in number portability query does not exist, return error value that indicates subscriber record nonexistence. 23

35 Application response process of Number portability Connection, release call, or continue operation can be applied in sequence as a response to initial DP operation. For correlation and dialogue maintenance between initial DP and its sequence operation, TCAP protocol function is provided Response process which is in case that the porting of called party number is confirmed as a result of NPDB inquiry of SCP for number portability query, applies the connect operation. The required parameter destination routing address is included. This parameter includes 1 called party number parameter. Other optional parameters can be included if needed As a result of NPDB inquiry of SCP for number portability query, response process, in case that present service has been canceled after the called party number has been ported out, applies the release call operation. Cause value of a required parameter, cause, is encoded as ported number and a diagnosis field is encoded as disconnected ported number A response process, in case that there is no called party number in NPDB as a result of NPDB inquiry of SCP for number portability query, applies continue process The relation corresponding to TCAP protocol Operation/Error and TCAP protocol for NP are corresponded as follows. Operation/Error TCAP message type Indication class Direction Initial DP operation Begin 2 SSP SCP Initial DP error End - SSP SCP Connect operation Continue 2 SSP SCP Connecting error Continue - SSP SCP release call operation End 4 SSP SCP 24

36 The correlations of transactions between initial DP operation and its response (sequence operation) should be maintained. Normal end for connect operation, indication class 2, is defined as standby end Guideline for the application of freephone service This section guides the part of freephone application process of SSP and SCP systems that changes are unavoidable because of number portability Freephone service query process Each service provider processes with initial DP operation based on the existing method, and no additional changes will be made by number portability Freephone service response process In case that the porting of relevant freephone number has been confirmed, responding with release call operation should be done in principle. But, if initial originating service provider of a call is identical, call connection operation can be used as a response instead of Release Call operation. - Cause value of cause parameter is encoded with ported number. - Diagnosis value of cause parameter is encoded with ported between networks (service provider portability). As a response to freephone service query, when receiving release call operation whose cause value is "ported number, SSP processes as follows. - When a diagnosis field of cause parameter has been omitted or the value has been encoded as "no indication" or "ported between networks (ported intelligent networks)," a release call message will be sent by front-end switch. 25

37 7. WIN (MAP) enhancements for number portability 7.1. Generals This chapter describes the cases when requiring supplementation is unavoidable because of number portability, in case of applying WIN (MAP) protocol instead of INAP when MSC processes NP query in mobile telecommunication network Relevant WIN (MAP) protocol will be supplemented by referring to criterions of number portability-related IS-756.A and intelligent network protocol-related IS-771 based on IS-41 which domestic mobile telecommunication providers have applied as a standard Z is additionally defined as a connection point between MSC and NPDB for supporting number portability in existing Map connection model. In this case, this connection point "Z" corresponds to INAP connection point "D" in Picture 1 since NPDB function includes the functions of L_SMS and NP_SCP in Picture Producer of operation and error Process of MSC and NPDB applies that of MSC and SCP in WIN respectively. 7.3 Parameter enhancements Use Number Portability Request (NPR)" operation for supporting number portability. 26

38 NPR operation Direction : MSC NPDB Timer : T npt ( Interim value 6 sec) Class : 1 Code value : local Value 62 Indication parameter (type:set) Required/ Reference Digits (Dialed) Required Corresponding to CdPN of INAP IDP Calling Party Number Digits l Corresponding to CdPN of INAP IDP MSCID MSC identifier being applied with NP query MSCID (Originating) Originating mobile station identifier Return result parameter (in case of NP Request succeeded in response) Routing Digits Required/ Return error code (in case of NP request failed to response) Apply or not Unrecognized MIN Unrecognized ESN MIN/HLR mismatch Operation sequence problem Resource shortage Operation not supported Trunk unavailable Parameter error System failure Unrecognized parameter value Feature inactive Missing parameter Disconnected ported number Reference Corresponding to DRA (CdPN) of INAP CON Reference Required digits (dialed) parameter is a number that is not included in currently usable DN range of NPDB Required MAP operation is received in NPDB but not recognizable. Required NPDB support is temporally not in service Parameter has encoding problem (Ex, Digits parameter has fault length field.) Required support (ex, DB access) is not accessible because of unexpected error. Provided parameter value is not recognizable or is not standard value. Parameter value (ex, MSCID) to be provided is not received. Correspondingto disconnected ported number of INAP 27

39 7.4. Signaling procedure Addition of "disconnected ported number (0 8D)" code to error code parameter should be considered There are no parameters to be changed/supplemented other than this Requirements of lower layer protocol Number portability query process (indication component) MSC indicates number portability request" operation to NPDB. Dialing Number (DN) should be included in digits (dialed) parameter as an indicate parameter. Other parameters can be selectively included Number portability success response process (return result component) NPDB transfers return result (final) component about success in number portability request" operation process to MSC. Translated Routing Number (RN)" should be included in routing digits parameter. If a subscriber number indicated as digits (dialed) parameter is not registered in NPDB (corresponding to subscriber record nonexistence error in INAP), NPDB transfers return result (final) component that is not including routing digits parameter to MSC Number portability failure response process (Return error code) NPDB transfers return error code about number portability request" operation process failure to MSC. If NPDB is temporally not usable, resource shortage error will be processed. 28

40 When NPDB has recognized number portability request" operation indication, but it does not support the process function, or required MSC does not have concerned authority, operation not supported error will be processed. If the parameter indicated by MSC has encoding problem, Parameter Error will be processed. In this case, an identifier of problematic parameter will be included in return error parameter. If the supports necessary for NPDB are inaccessible because of present breakdown, system failure error will be processed. In this case, involvement of NPDB administrator or maintenance personnel is requested for restoring breakdown. In case of a parameter indicated by MSC is not verifiable or has invalid code value, unrecognized parameter value error will be processed. In this case, an identifier of problematic parameter will be included in return error parameter. If NPDB has not received option parameter required to be received, Missing Parameter error will be processed. In this case, an identifier of problematic parameter will be included in return error parameter. 3 When relative subscriber has disconnected ported number, disconnected ported number will be processed Number portability non-response process This corresponds to the case that any response has not been received from NPDB for "number portability request" operation indication of MSC. INAP IDP operation will be processed based upon occurrence of non-response. 3 If required parameter is not received, the rejection with query code of "incorrect parameter" will be processed. 29

41 7.6. Low protocol requirements Apply domestic TCAP, SCCP and MTP protocol requirements as it is, which the existing WIN (MAP) have applied. 8. CAP enhancements for number portability 8.1 General This chapter describes the items required to be supplemented because of number portability in case of applying CAP protocol instead of INAP when MSC (SSP) processes NP query in mobile telecommunication Relative CAP protocol is supplemented by referring to 3GPP specification (TS22.078M TS23.078, TS29.078). 8.2 Operation procedure General It also uses initial DP, connection and release call operations of CAP as a signaling connection between MSC (SSP) and SCP for portability application Number portability application does not need signaling connections between MSC (SSP)/SCP and IP system, and assumes SDF function entities to be unified within SCP system Besides operation defined in this standard, non-call related management operation (ex. call gapping) can be additionally used if necessary Initial DP operation General 30

42 This operation is applied for number portability query and directed from MSC (SSP)[CCPF] to NPDB[NPCF]. Called party number parameter must be included for number portability application as mandatory and this parameter is used in number portability database inquiry. The rest of parameters are applied as an option parameter based on CAP standard Operation definition Initial DP operation Direction : MSC (SSP)[CCPF (SSF)] Timer : T idp Class : 2 Code value : localvalue 0 NPDB[NPCF (SCF)] Initial DP parameter (type:sequence) Required/ Reference Service key Called party number Calling party number Calling party category CallGap encountered IP SSP capabilities Location number Original called party ID High layer compatibility Additional calling party number Bearer capability Event type BCSM Redirecting party ID Redirection information Cause Service interaction indicators two Carrier CUG index CUG interlock code Outgoing access indicator IMSI Subscriber state Location information Ext-basic service code Call reference number MSC address Called party BCD number Time and time zone GSM forwarding pending GMSC address Extension Required Required NP application required 31

43 Error Subscriber record nonexistence Parameter nonexistence Parameter out of range System breakdown Operation rejection Unexpected component sequence Unexpected data value Unexpected parameter Abstract Syntax Notation No.1 (ASN.1) Initial DP {PARAMETERS-BOUND : bound} OPERATION ::= { ARGUMENT initial DP parameter {bound} RETURN RESULT FALSE ERRORS {subscriber record nonexistence Parameter nonexistence ParameterOutOfRange System breakdown Operation rejection Unexpected component sequence Unexpected data value Unexpected parameter CODE opcode-initialdp } 32

44 Initial DP parameter {PARAMETERS-BOUND : bound} ::=SEQUENCE { Service key [0] Service key, called party number [2] called party number {bound}, originating number [3] originating number {bound} Originating class [5] Originating class Call gapping sensing [7] Call gapping sensing IPSSP capability [8] IPSSP capability {bound} Location number [10] Location number {bound} Initial called party number [12] Initial called party number {bound} Extension [15] SEQUENCE SIZE (1..Extension number) OF extension field {bound} High layer compatibility [23] High layer compatibility Additional originating number [25] Additional originating number {bound} Bearer capability [27] Bearer capability {bound} BCSM case type [28] BCSM case type Call transfer originating number [29] Call transfer originating number {bound} Call transfer information [30] Call transfer information Cause [17] Cause {bound} Service interaction indicator [32] Service interaction indicator Service provider [37] Service provider information {bound} CUG index [45] CUG index CUM integration code [46] CUG integration code Originating connection indicator [47] NULL IMSI [50] IMSI Subscriber condition [51] Subscriber condition Location information [52] Location information Basic service code [53] Basic service code Call reference number [54] Call reference number MSC address [55] ISDN address character string Destination BCD number [56] Destination BCD number {bound} Time and time zone [57] Time and time zone {bound} GSM forwarding pending [58] NULL Initial DP Extension [59] Initial DP Extension } Initial DP Extension ::= SEQUENCE { GMSC address[0] ISDN address character string OPTIONAL } Application entity process Process of MSC (SSP)[CCPF] and NPDB[NPCF] applies that of gsmssf and gsmscf in WIN respectively Connect operation 33

45 General This operation is applied as a normal sequence operation for initial DP operation, and destination routing address parameter is included in principle. This parameter includes called party number and the number includes addresses for routing to destination side for MSC (SSP)[CCPF]. The rest of parameters apply as option parameters according to INAP standard criterion. In case that a called party number indicated on initial DP operation in number portability application has been ported, a destination parameter of this operation uses it for transferring final destination switch or identifying address of final destination network which the ported number has been serviced to. Operation definition Connect operation Direction : NPDB[NPCF (SCF)] Timer : T con Class : 2 Code value : localvalue 20 connection parameter (type:sequence) Destination routing address Page type Initial called party number service provider Originating class Call transfer originating number Call transfer information General number Service interaction indicator Pay number CUG integration CUG originating connection Announcement restrict ocsi application Pay number type Extension MSC (SSP)[CCPF (SSF)] (Destination routing address) (Alerting pattern) (Original called party ID) (Carrier) (Calling party category) (Redirecting party ID) (Redirection information) (Generic number) (Service interaction indicators two) (Charge number) (CUG interlock code) (Outgoing access indicator) (Suppression of announcements) (O-CSI applicable) (NA originating line information) Required/ Required Reference NP applicati on required 34