Você está na página 1de 16

FUNCTION SPECIFICATION

Uppgjord Prepared Datum Date Rev

1 (16)

Dokumentnr Document no

ESF F. Fauvet
Godknd Approved Kontr Checked

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

ESF F. Vergnaud

MOBILE ORIGINATED ACTIVE SPEECH CALL REROUTING IN MSC/VLR


Contents 1 1.1 1.2 1.3 1.4 2 2.1 2.2 2.3 2.4 2.5 2.6 3 3.1 3.2 3.3 3.4 3.5 General Information Introduction Revision Information References Concepts Function Description Signalling diagram Bnumber analysis Restart Supplementary services interactions Required signalling informations Operational Conditions External Conditions Subscriber Procedures Subscriber Categories Charging Capabilities

omnifilter R5A

FUNCTION SPECIFICATION
Datum Date Rev

2 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

1
1.1

General Information
Introduction
This function enables a calling mobile mobile subscriber to establish a speech call to an assistance operator and request the Bparty number and to get automatically the speech connection with this Bparty after call rerouting in the originating mobile exchange.

1.2

Revision Information
G>H The document is updated to include Chapter 2.6.2 DSS1 expected external Cause and location code. F>G The document is updated to include the applicability of ACR initiated on a DSS1 link E>F Chapter 2.6.2 added. Description of cause and location informations. D>E Description of the interaction with the CAMEL feature is added. C>D Description of the interaction with the Remote control Equipment Subsystem (RES) functionnality is added. B>C The function is modified to take into account the interactions with IN servi ces The references are corrected A>B The document is updated to include the applicability to ISUP

1.3

References
(1) SS7 Telephone User Part Plus for French Mobile Application 1/155 17CRTCM 212 0004 rev.A (2) AInterface , Section K: Direct Transfer Application Part, in MSC/VLR DTAP, Message format and coding for call control and related supple mentary service procedures 12/155 171/APT 210 25/5 rev.A (3) ISDN USER PART 4, SECTION A, FORMAT AND CODES 2/155 17CRT 212 31/11 rev.A

FUNCTION SPECIFICATION
Datum Date Rev

3 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

(4) Line Interface Administration Handler Changeable Exchange Adaptation 2/155 18CNT 288 1058 Uen A (5) DSS1 LAYER 3 PROTOCOL SPECIFICATION, MESSAGES AND INFORMATION ELEMENTS FOR BOTH BASIC CALL AND SUPPLE MENTARY SERVICE CONTROL, ISDNE 9/155 17CRT 288 01 Uen D

1.4

Concepts
Bparty number: the directory number of the subscriber that is called by the mobile subscriber requesting the service. Rerouted call: The call is first directed to operator and then rerouted to B party number Operator code: The operator code is the value of the SII parameter introdu ced in the Bnumber analysis for the operator service.

FUNCTION SPECIFICATION
Datum Date Rev

4 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

2
2.1

Function
Description
The function is invoked when a mobile subscriber establishes a speech call to an operator. The service should be requested by operator using special signalling information in the release procedure. This function makes use of the UsertoUser Signalling service 1 (implicit).

network (2) (4)

towards operator exchange (3)

(5) MSC/VLR (1) MS network towards B party

(1) (2) (3) (4) (5)

MS subscriber dials number to directory service MSC establish speech call towards operator position through network using french TUP+ message IAF or ISUP IAM message containing operator code in User to user field. MS subscriber asks for B party to operator Operator releases the call giving B party number information in User to user field of french TUP+ CBU message or ISUP REL message which is transited in the network Originating MSC releases outgoing side and keeps A interface ressources MSC analyses received B party number and set up a new outgoing call

FUNCTION SPECIFICATION
Datum Date Rev

5 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

2.2
2.2.1

Signalling diagram
ISUP/SSUTR2

MS/BSS BSSAP

MSC/VLR Fr.TUP+ or ISUP

< NATIONAL OPERATOR CALL SET UP> SET UP ==================> (speech, called = B operator) CALL PROCEEDING <================== ASSIGNMENT REQ. <================== (speech TCH) ASSIGNMENT COMPL. ==================> ....................... < NORMAL CALL TO OPERATOR> ////////////////////////////////////////////////////////////////////////// ///////////////////////////////SPEECH///////////////////////////////////// ////////////////////////////////////////////////////////////////////////// /////////////////// <supervision state> // NOTIFY (2) //// CBU or REL <================== Call re arrangement. <================= ///(suspend)/////// (U2U = B id (1)) /////////////////// Immediate network release. CLU or RLC /////////////////// ==================> /////////////////// /////////////////// IAF /////////////////// New outgoing trunk. ==================> /////////////////// (for ex. using F TUP+) (B id) /////////////////// /////////////////// // NOTIFY ////// ACF <================== <================= // (resume) /////// /////////////////// AUU /////////////////// <================= ////////////////////////////////////////////////////////////////////////// ///////////////////////////////SPEECH///////////////////////////////////// ////////////////////////////////////////////////////////////////////////// Notes: (1) After identifying the Bparty number, the operator releases the call with French TUP+ CBU message (Clear Back with User to User Info ) or ISUP REL message containing the Bparty number preceded by operator code in User to User field. Upon reception of this message, the originating MSC releases the outgoing side keeping the mobile side established and originates a new outgoing call IAF or IAM ====================> (called = B operator, calling = A id U2U=operator code)

ACF or ACM <==================== (called address RNIS)

FUNCTION SPECIFICATION
Datum Date Rev

6 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

towards Bparty. (2) At beginning of rerouting call setup, the MS receives a notification and the call state remains unchanged for the mobile. No progress tone neither announcement will be provided to mobile during this phase of call. After reception of ACF or ACM, MS will receive a new notification and will be able to receive announcement or tone given by terminating exchange.

FUNCTION SPECIFICATION
Datum Date Rev

7 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

2.2.2

DSS1

MS/BSS BSSAP SET UP ===============> (speech, called=operator) CALL PROCEEDING <=============== ASSIGNMENT REQ. <=============== (speech TCH) ASSIGNMENT COMPL ===============>

MSC/VLR

TSC SSUTR2 or ISUP

Operator DSS1

< NATIONAL OPERATOR CALL SET UP>

IAF or IAM SETUP =================> ==================> (called=operator, (called=operator, calling = A id calling = A id U2U=operator code) U2U=operator code)

ALERTING ACF or ACM <================== <================= (called addr RNIS) CONNECT AUU or ANM <================== <================= < NORMAL CALL TO OPERATOR> ////////////////////////////////////////////////////////////////////////////// ///////////////////////////////SPEECH///////////////////////////////////////// ////////////////////////////////////////////////////////////////////////////// //////////////// DISCONNECT // NOTIFY (3) / CBU or REL <================== <=============== Call re arrangement <================= (U2U = B id (1)) ///(suspend)//// (U2U = B id (2)) //////////////// //////////////// Immediate network CLU or RLC RELEASE //////////////// release =================> ==================> //////////////// //////////////// RELEASE COMPLETE //////////////// <================== //////////////// IAF //////////////// New outgoing trunk. ==================> //////////////// (e.g. using F TUP+) (B id) // NOTIFY /// ACF <=============== <================= // (resume) //// //////////////// AUU //////////////// <================= ////////////////////////////////////////////////////////////////////////////// ///////////////////////////////SPEECH///////////////////////////////////////// ////////////////////////////////////////////////////////////////////////////// Notes: (1) After identifying the Bparty number, the operator releases the call with DSS1 DISCONNECT message containing the Bparty number preceded by operator code in User to User field. This number is encoded is IA5 format. (2) Upon reception of this message, the TSC releases the call with French TUP+ CBU message (Clear Back with User to User Info ) or ISUP REL message containing the Bparty number preceded by operator code in User to User field. This number is encoded in BCD format.

FUNCTION SPECIFICATION
Datum Date Rev

8 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

Upon reception of this message the originating MSC releases the outgoing side keeping the mobile side established and originates a new outgoing call towards Bparty. (3) At beginning of rerouting call setup, the MS receives a notification and the call state remains unchanged for the mobile. No progress tone neither announcement will be provided to mobile during this phase of call. After reception of ACF or ACM, MS will receive a new notification and will be able to receive announcement or tone given by terminating exchange.

2.3

Bnumber analysis
The Bnumber analysis shall be modified in the following way: a special SII parameter is used to define the operator code for mobile originated directory service calls. The use of this function is then limited to the numbers where a SII indication is set. The value of SII shall be chosen between H0001 and H9999 with decimal digits. ANBSI=B100zabpqmcdu,SII=Hwxyz,RC=....; zabpqmcdu is the directory number for the operator service For the rerouting call, the Bnumber (without operator code) given by the operator in the release message, is analysed in the Bnumber origin for preanalysis defined in IMSIS table. For calls involving IN refer to chapter 2.5.6

FUNCTION SPECIFICATION
Datum Date Rev

9 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

2.4

Restart
If a small restart occurs during the rerouting call, the MS side is released as the call is considered as unstable.

2.5
2.5.1

Supplementary services interactions


Call barrings
The operator determined barrings and barring supplementary services applies normally to the rerouted call.

2.5.2

Call forwardings
No interaction. The rerouted call can be forwarded afterwards.

2.5.3

Calling line identity services


No interaction

2.5.4

Call hold, call waiting, multiparty call


These are rejected when using this function.

2.5.5

Usertouser signalling
The interaction of this function with the Usertouser services of GSM phase 2+ is for further study.

FUNCTION SPECIFICATION
Datum Date Rev

10 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

2.5.6

IN services
In order to enable the use of this function for users subscribing to IN servi ces needing a particular numbering plan (such as VPN, using an escape code), a specific treatment is achieved for mobile subscribers having an Originating IN Category Key service. The call to operator may invoke or not the IN, depending of IST in B number analysis for operator number. The operator code (SII) may be placed in Bnumber analysis before triggering SSF function. When the operator releases the call with the rerouting Bnumber in front of which operator code is appended, if the mobile subscriber has an OICK mark, the operator code is kept for Bnumber analysis. Then the following number is sent for analysis in the Bnumber origin pointed by MIN route: OICK + operator code + Bnumber, allowing a parti cular treatment depending on the IN service (for example for VPN the operator code can be replaced with escape code). Charging The Bnumber in the charging record will be without operator code: OICK + Bnumber.The operator code (SII) may be placed in Bnumber analysis before triggering SSF function. In the same way

2.5.7

CAMEL (Phase 1 & 2)


As CAMEL is a network feature providing generic capability based on IN principles, the use of Active Call Rerouting function is possible as well under the same specific treatment performed for OIN/TIN/OICK/TICK based IN services. The difference introduced with CAMEL take place in the triggering mecha nism based on the CSI (Camel Subscription Information) mark assigned to the subscriber. The call to operator from a CAMEL subscriber should invoke CAMEL. The operator code (SII) will be placed in Bnumber analysis before triggering SSF function. When the operator releases the call with the rerouting Bnumber, the operator code appended to this Bnumber should be removed at Bnumber analysis. The rerouted call will invoke CAMEL a second time. The Called Party BCD Number present in the IDP operation will include the operator code (SII) + the Bnumber Charging The Bnumber in the MSO charging record will be with operator code : operator code (SII) + Bnumber.

2.5.8

RES service

FUNCTION SPECIFICATION
Datum Date Rev

11 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

Handling of calls under the Remote control Equipment Subsystem (RES) is now supported. In case of originating subscriber RES monitoring, the initial call and the rerouted one are handled as two separate transactions from RES function point of view. In case of terminating subscriber RES monitoring, the rerouted call is moni tored as AB speech connection.

FUNCTION SPECIFICATION
Datum Date Rev

12 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

2.6
2.6.1

Required signalling informations


Structure of Usertouser field

IEI (1)

Information element User user Length

Presence Format Length M M M M TLV L V LV 1 1 1 3 31

41

Protocol dicriminator User user info 2)

Note 1: The coding H7E for H20 for H7E for

of USER USER information element is: F TUP+, the field is included in Access Data ISUP DSS1

Note 2: User user info contents: in IAF or IAM the operator code (value of SII parameter) in CBU or REL the Called Party number of rerouting number encoded in BCD format in SETUP the operator code in DISCONNECT the Called Party number of rerouting number encoded in IA5 format

FUNCTION SPECIFICATION
Datum Date Rev

13 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

Called Party BCD Number The purpose of the called party BCD number IE is to identify the called party. The called party BCD number IE is coded as shown below.

8 0

1 octet 1 octet 2 octet 3 octet 4 octet 5 : :

1 0 1 1 1 1 0 Called party BCD number IEI Length of called party BCD number contents

1 ext

type of number Number digit 2 Number digit 4

Numbering plan identification Number digit 1 Number digit 3

Called party BCD number IE. Refer to DTAP Functionnal specification (ref. 2) for the detailed coding of Called Party BCD number number. The operator code digits precede the Bsubscriber number digits.

FUNCTION SPECIFICATION
Datum Date Rev

14 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

Called Party IA5 Number The purpose of the called party IA5 number IE is to identify the called party. The called party IA5 number IE is coded as shown below.

8 0

1 octet 1 octet 2 octet 3 octet 4 octet 5 : :

1 1 1 0 0 0 0 Called party IA5 number IEI Length of called party IA5 number contents

1 ext

type of number

Numbering plan identification Number digit 1 Number digit 2

Called party IA5 number IE. The operator code digits precede the Bsubscriber number digits.

FUNCTION SPECIFICATION
Datum Date Rev

15 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

2.6.2

Cause and location informations


Here below is summurized the expected values for cause and location informations expected from release signalling messages ( CBU in FTUP+, REL in ISUP, DISC or REL in DSS1).

FTUP+ Cause code External value Location code External value Not applicable Deduced from CBU Not applicable Deduced from CBU

ISUP 16=Normal call clearing 10=Network beyond interworking point

DSS1 16=Normal call clearing All location code supported Note 1

External cause value 16 and location value 10 are respectively mapped in internal AXE values 3 and 10. All others values for external cause and location which do not fullfill this internal mapping will lead to the disconnection of the call. Note 1: DSS1 access must have access parameter LOCMAP set to LOCMAP3 in order to have a correct mapping of location value to 10. Application Information of function block LIADM (ref. 4) is changed. Access parameter LOCMAP3 leads to a mapping towards location 10 (Network beyond interworking point).

FUNCTION SPECIFICATION
Datum Date Rev

16 (16)

Dokumentnr Document no

20021120

15517MET/M/TS96:0048 Uen
Tillhor / referens File / Reference

3
3.1

Operational Conditions
External Conditions
The function uses the SS7 Telephone User Part Plus signalling or ISUP signalling or DSS1 signalling for outgoing routes towards operator (see ref. 1, 3 and 5)

3.2

Subscriber Procedures

3.3

Subscriber Categories

3.4

Charging
Depending on exchange data (charging case analysis), the operator call may be charged or not. The rerouted call to Bparty is charged as normal mobile originated call. There will be no indication that the call was rerouted except the one descri bed in chapter 2.5.7.

3.5
3.5.1

Capabilities
General
This function applies to speech teleservice only. This service may be used by all mobile subscribers registered in MSC/VLR.