Basic Call Scenario

8/13/2019 Basic Call Scenario

1/106

3GPP TS 32.250 V9.1.0 (2010-03)Technical Specification

3rd Generation Partnership Project;Technical Specification Group Service and System Aspects;

Telecommunication management;Charging management;

Circuit Switched (CS domain charging(!elease "

The present document has been developed within the 3rdGeneration Partnership Project (3GPPTM) and may be further elaborated for the purposes of 3GPP.

The present document has not been subject to any approval process by the 3GPP Orani!ational Partners and shall not be implemented.

This "pecification is provided for future development wor# within 3GPP only. The Orani!ational Partners accept no liability for any use of this

"pecification."pecifications and reports for implementation of the 3GPPTMsystem should be obtained via the 3GPP Orani!ational Partners$ Publications Offices.


2/1063GPP

%eywordsUMTS, charging, management

3GPP

Postal address

3GPP support office address

650 R!te "e# $!ci%e# - S&hia 'nti&%i#

Va%nne - R'*+Te%. 33 / 92 9/ /2 00 a 33 / 93 65 / 16

&nternet

htt&.3g&&.rg

Copyright Notification

'o part may be reproduced ecept as authori!ed by written permission.

The copyriht and the foreoin restriction etend to reproduction in all media.

*+,+- 3GPP Orani!ational Partners (/&0- T&"- 11"- 2T"&- TT- TT1).

ll rihts reserved.

MT"4 is a Trade Mar# of 2T"& reistered for the benefit of its members

3GPP4 is a Trade Mar# of 2T"& reistered for the benefit of its Members and of the 3GPP Orani!ational Partners

5T24 is a Trade Mar# of 2T"& currently bein reistered for the benefit of its Members and of the 3GPPOrani!ational Partners

G"M6 and the G"M loo are reistered and owned by the G"M ssociation

3GPP TS 3#$#%& '"$$& (#&&)&3#!elease "


3/106

+ntent#

1ontents....................................................................................................................................................3

7oreword...................................................................................................................................................8

, "cope......................................................................................................................................................9

* /eferences..............................................................................................................................................9

3 :efinitions- symbols and abbreviations..................................................................................................;3., :efinitions..............................................................................................................................................................;

3.* "ymbols..................................................................................................................................................................ih level 1" domain architecture......................................................................................................................,*

=.* 1" domain offline charin architecture.............................................................................................................,3=.3 1" domain online charin architecture..............................................................................................................,=

8 1" domain charin principles and scenarios......................................................................................,88., 1" domain charin principles............................................................................................................................,8

8.,., General aspects of 1harin :ata.....................................................................................................................,88.,.* 1harin information....................................................................................................................................... .,8

8.,.*., "ubscriber billin...........................................................................................................................................,98.,.*.* "ettlements of 1hares...................................................................................................................................,9

8.,.*.*., &nter?P5M' accountin..............................................................................................................................,98.,.*.*.* @Aisitors@ from other P5M's................................................................................................................. ....,9

8.,.*.*.3 @>ome@ subscribers roamin in other P5M's...........................................................................................,98.,.*.*.= "ettlement with other networ#s...................................................................................................................,9

8.,.*.3 "ervice &nformation........................................................................................................................................,B8.,.3 "pecial cases and considerations.......................................................................................................................,B

8.,.3., o1 service.................................................................................................................................................. ..,B8.,.3.* 1M25 services.......................................................................................................................................... ..,;

8.,.3.3 se of supplementary services.......................................................................................................................,;

8.,.3.= se of call forwardin....................................................................................................................................,;8.,.3.8 se of call hold and multi?party services.......................................................................................................,;

8.,.3.9 Partial records.................................................................................................................................................,5/). Thus- the 1" nodes are connected directly to the 0illin :omain via the 0c

reference point. This implies that there eists no separate 1:7 and 1G7 for the 1" domain- and no correspondin openinterfaces between any such functions- within the 3GPP standards.

>owever- vendors may choose to implement separate 1:7 and 1G7 for the 1" domain. &n that case- the interfaces

between these functions should comply with the definition of the /f and Ga reference points (3GPP T" 3*.*


15/106

5 +S "main charging &rinci&%e# an" #cenari#

5.1 +S "main charging &rinci&%e#

The followin hih?level reCuirements summari!e the more detailed reCuirements of 3GPP T" **.,,8 ,+*H.

,. to provide a 1:/ for all chares incurred and reCuirin settlement between the different commercial rolesE

*. to allow itemi!ed billin for all services (includin 1M25) chared to each subscription- includin voice and

data calls- and services offered by home environments- ta#in into accountD

? information provided by the user (includin authentication parameters- etc.)E

? information provided by the servin networ# (includin "ervin 'etwor# &d- timestamps- etc.)E

? information provided by the service (includin chared party- lon callin- multimedia- etc.).

3. to allow fraud control by the >ome 2nvironment and the "ervin networ#.

5.1.1 Genera% a#&ect# 4 +harging ata

1harin :ata /ecord (1:/) eneration and contents should be fleible and unnecessary redundancy in data should be

avoided. 1harin data are collected for successful and selected unsuccessful subscriber transactions. The subscribertransaction is seen as bein successful in the M"1 server (where the 1:/ is enerated) either if a call is answered or if

the "hort Messae "ervice 1entre has confirmed the successful receipt of a mobile oriinated short messae.

nsuccessful call attempts are recorded in the case of partial record eneration due to 1M25 7ollowOn1alls. &f in

such a call constellation the answer state is reached at least once- subseCuent unsuccessful set?up of a connectionconfiuration is also recorded in order to provide a complete seCuence of 7&/"T- &'T2/M2:&T2 and 5"T records.

t termination of the subscriber transaction these data are formatted into 1:/s. These records are forwarded onto M"1

server$s 1G7 which constitutes the source for further transportation of that data to the 0illin :omain via the 0creference point- see 3GPP T" 3*.*


16/106

2ach 1:/ captures all charin information relevant to the call- or in case of partial 1:/s (see clause 8.,.3.9)- theportion of a call that the 1:/ covers. :ependin on the type of 1:/ and the node producin it- this includes

information on tele? and bearer services (which may include radio resource usae) and supplementary serviceinvocation F termination. s far as tele? and bearer services are concerned- all service information is embedded in the

appropriate 1" 1:/- i.e. there are no specific @service 1:/s@ in the 1" domain. 7or "upplementary "ervices- the eacttreatment is specified in clause 8.,.3.3.

&n addition to the information collected from the networ# elements- networ# manaement functions are reCuired for theadministration of on?line charin data stored in the M"1 servers. This data is employed to drive the chare display in

the Mobile "tation (M") as reCuired by the dvice of 1hare (o1) service and defined by 3GPP T" **.+;9 *+=H and3GPP T" **.+*= *+3H.

5.1.2.1 S!#crier i%%ing

The charin data collected from the >P5M'- interroatin P5M'- andFor AP5M' networ# elements is employed to

determine the networ# utili!ation chares for the basic and supplementary services utili!ed by the home subscribers of

the P5M'. The chares calculated are then combined with the networ# access (subscription) chares and billed to thosecustomers directly serviced by the P5M'.

7or those subscribers handled by "ervice Providers- the billin information is employed for both wholesale ('etwor#

Operator to "ervice Provider) and retail ("ervice Provider to "ubscriber) billin. 1onseCuently- havin been processedby the P5M' 0illin "ystem- the charin data collected from the networ# elements may also be sent to the "erviceProvider for further processin.

5.1.2.2 Sett%ement# 4 +harge#

5.1.2.2.1 :nter-P$M* acc!nting

&nter?P5M' accounts for roamin traffic are determined in accordance with &T?T principles (see &T?T

/ecommendation :.


17/106

? sinallin (MPF"11P- 1PF"11P) traffic such as location updates.

ccountin information may also be reCuired for the use of services provided by other operators such as short messae

service centres and other Aalue dded "ervice (A") providers.

The chares for the various traffic shares may be determined on the basis of the 1:/s enerated by the networ#

elements or on the basis of bul# counters (accountin meter records) in the ateway M"1 servers (GM"1 servers). 7or

the purpose of the present document- the manaement information reCuired is assumed to be derived from 1:/s. Themanaement of accountin meters is outside the scope of the present document.

&n G"M- the radio resources used for various connection types are rouhly identical- hence no differentiation of the

connection types is needed for the purpose of inter?networ# accountin. &n MT"- however- the radio bandwidthallocated to a connection may be much hiher compared to G"M- even thouh the connection loo#s identical from the

perspective of the ateway M"1 server. Therefore it is necessary that the ateway 1:/s capture the cases where@hiher?than?normal@ radio bandwidth is occupied. n eample of a narrow band radio connection is the standard M/

voice call. n eample of a wideband service- usin the same landline channel but much more radio resources- is theuse of 0"3+ for video telephony.

Given that ? in contrast to the servin M"1 server ? the ateway M"1 server cannot distinuish the cases describedabove- the servin M"1 server is capable of returnin information on the bearer capability bac# to the GM"1 server so

that this information can be added to the ateway 1:/ for incomin connections. 7or further details of thisfunctionality- refer to 3GPP T" *


18/106

5.1.3.2 +'M$ #er7ice#

1M25 service can be activated for oriinatin- forwarded and terminated calls and oriinatin "M". "everal fieldsdescribin 1M25 subscription and free format data are recorded to appropriate 1:/. 7or oriinatin and forwarded

calls two different 1M25 services can be active and part of stored information is different dependin on the 1M25call model and which triers occur. 1M25 fields describin usae level of service- 1M25 modified parameters

and 1M25 initiated call forwardin include information for one call le includin impacts on all 1M25 services.

5.1.3.3 U#e 4 #!&&%ementar #er7ice#

The recordin of supplementary service usae permits the 0illin :omain (0:) to specify the supplementary service

actions (invocation- reistration- etc.).

&n addition to specifyin the actions to be recorded- the 0: may also determine how these events are to be recorded.

'on?call related events- such as the administration of supplementary services by the subscriber via the MM& of the M"-shall result in the production of supplementary service action records. 1all related events (e.. invocation of

supplementary services) shall be recorded @in?line@ in the appropriate 1:/ and F or in a separate ""?action recorddependin on the confiuration specified by the 0:.

Ihere the use of a supplementary service results in the production of further connections (e.. call forwardin-

multi?party service etc.) additional 1:/s shall be produced to describe the relevant connections. The use of suchservices is described in more detail both in this clause and in the eample scenarios.

5.1.3./ U#e 4 ca%% 4rar"ing

Ihen one of the call forwardin services is used- the charin function of the M"1 server that forwards the call- shall

produce the MO1 record for the forwarded part of the call.

7or further information concernin the recordin of call forwardin services see the eample scenarios in

clauses 8.*.,.9 and 8.*.,.B.

5.1.3.5 U#e 4 ca%% h%" an" m!%ti-&art #er7ice#

The use of the call hold service shall be recorded either in?line in the appropriate 1:/ or in a separate supplementaryservice @invocation@ record as described above. The duration for which the call is held- i.e. is inactive- is not recorded.

The use of the multi?party service reCuires a minimum of 3 subscribers and the use of a conference circuit. 7or the

purpose of the followin description the subscriber invo#in the service is referred to as the conference oriinator (@@)and the conference call is rearded as consistin of a number of individual @les@ between the conference oriinator and

the other parties (@0@- @1@- etc.) in the call.

'ormal MO1 and MT1 1:/s shall be enerated for each party and each le of the call. &n addition- if common

eCuipment records are enabled- a common eCuipment record shall be produced for the conference oriinator in order torecord the use of a conference bride and to record the total duration of the conference connection.

2MP52D "ubscriber @1@ calls subscriber @@. "ubscriber @@ places the call from @1@ on hold and ma#es asecond call to subscriber @0@. "ubscriber @@ then invo#es the multi?party service in order to

set?up a conference call with @0@ and @1@.

ssumin that the appropriate types of record are enabled- the followin 1:/s shall be producedD

? n MO1 record for subscriber @1@ and the @1@?N@@ le of the callE

? n MT1 record for subscriber @@ and the @1@?N@@ le of the callE

? n MO1 record for subscriber @@ and the @@?N@0@ le of the callE

? n ""?ction record for the invocation of the call hold service by subscriber @@E

? n MT1 record for subscriber @0@ and the @@?N@0@ le of the callE

? n ""?ction record for the invocation of the multi?party service by subscriber @@E

? common eCuipment record for the use of the conference bride by subscriber @@.

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3-!elease "


19/106

2ach of the MO1FMT1 records for the conference oriinator (@@) shall include the supplementary service code for themulti?party service.

ny subseCuent action affectin only one le of the connection shall be recorded either in a separate supplementaryservice action record or in?line in the appropriate 1:/. ny action affectin the conference as a whole e.. the

oriinator holdin the conference shall be recorded either in a separate supplementary service action record or in the

common eCuipment usae record.

7or further information concernin the recordin of multi?party services see the eample scenario in clause 8.*.,."1": Parameters (for G"M only) durin a callE

? chane of 1M25 destination (1M25 controlledFinitiated) durin a callE

? 1M25 1P> operations on call les.

ll partial records for the same connection shall contain the same call reference and shall be ordered via a runnin

seCuence number. The time stamps involved shall apply to the individual partial records rather than the connection as awhole i.e. the @end@ time stamp (duration) of one record shall- in eneral- coincide with the @start@ time stamp (answer

time) of the net. 2ach time a new partial record is created the cause for termination field of the previous record shallcontain the value @partial record@. The cause for termination of the final partial record shall contain the true cause for

termination of the connection.

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3"!elease "


20/106

&t should be noted that the records produced in case of call re?establishment are not contiuous and that the value of thecause for term field in the record that is closed on radio lin# failure contains the value @partial record call re?

establishment@.

The partial records enerated may repeat each of the non?varyin fields contained in the oriinal record. lternatively- a

form of reduced partial record may be enerated which includes only those fields reCuired to identify the oriinal record

toether with the field(s) that actually chane.

5.1.3. U#e 4 circ!it-#itche" "ata #er7ice#

&f data services are employed in conjunction with a Pac#et?"witched Public :ata 'etwor# (P"P:') then anMO1FMT1 1:/ may be produced in the oriinatinFterminatin M"1 server and a ateway record in the

atewayFinterwor#in M"1 server. &f the pac#et volume is not available within the P5M' then this information may

also be provided in the form of a 1:/ from the P"P:'. &n such cases the 0illin "ystem is responsible for thecorrelation of the various records describin the connection. The definition of such P"P:' 1:/s is outside the scope

of the present document.

5.1.3.= :nter-MS+ #er7er han"7er

&n the case of an inter?M"1 server handover the controllin M"1 server- as defined by 3GPP T" *3.++< 98H- remains

in control of the connection and shall therefore- produce the 1:/. 7or the avoidance of doubt- it is not necessary toproduce 1:/s in the subseCuent M"1 server(s).

5.1.3.9 +a%% re-e#ta%i#hment

&n case of radio lin# failure as described in 3GPP T" *=.++; 9;H- the M" may attempt to re?establish the call usin the

procedures described in 3GPP T" *=.++; 9;H.

7or the time period between the detection of the radio lin# failure by the mobile station and the successful

re?establishment of the call- the advice of chare function in the M" is suspended as described in 3GPP T" *=.+;9 *3H.&n order to minimi!e the difference in chares between the on?line calculations performed by the M" and the off?line

processin on the basis of the 1:/s- it is necessary to eclude the time ta#en for the re?establishment phase from thechareable duration stored in the 1:/s.

&f the re?establishment attempt fails then an ordinary 1:/ (MO1FMT1) shall be produced with the cause fortermination value @stable call abnormal termination@. The chareable duration stored in this record covers the time

period from @nswer@ to the detection of the radio lin# failure by the M"1 server.

&f- the attempt to re?establish the call succeeds then the current 1:/ shall be closed with the cause for termination value

@partial record call re?establishment@ and a new partial record shall be opened for the re?established call. The chareableduration stored in the oriinal record is once aain the time period from @answer@ to detection of the radio lin# failure

by the M"1 server. 0oth the @sei!ure@ and @answer@ times of the subseCuent partial record correspond to the time atwhich the new traffic channel is allocated for the re?established call.

7urther radio lin# failures durin the re?established call may result in the eneration of additional partial records as

described above. ll of the partial records belonin to the same connection are identified by the same call referenceand a runnin seCuence number.

'OT2D s the M" and M"1 server may detect the radio lin# failure at different points in time- it is not possible

to uarantee that the duration used for the O1 display corresponds to that recorded in the 1:/s. Thepurpose of the above procedure is merely to minimi!e any discrepancies that may occur.

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3#&!elease "


21/106

5.1.3.10 Re#tricte" "irectr n!mer#

&n addition to the information pertainin to the served mobile subscriber (&M"&- M"&":'- etc.)- the 1:/s defined inthe present document also contain the directory numbers of other parties involved in the recorded connections or

transactions. &n order to comply with data protection leislation- it is necessary to distinuish between those numbersthat may be passed on to third parties and those that needs to be handled confidentially. s a result- each of the number

fields (e.. callinFconnected number) contains the presentation and screenin information defined in bothT" *=.++; 9;H and &"P sinallin. &f this information is supported by the networ#- then even restricted numbers may

be included in the appropriate records and suppressed off?line by the administration or billin system. &f thisinformation is not supported then the entire directory number shall be suppressed by the M"1 serverFA5/.

5.1.3.11 :M: >#er7atin

&n order to provide the data reCuired by the mobile eCuipment manaement activities outlined in the previous clauses-the M"1 server shall be capable of producin &M2& tic#ets for each of the followin eventsD

usae of a blac#listed &M2&E

usae of a reylisted &M2&E

usae of an &M2& not found on the white list.

n observed &M2& tic#et is enerated whenever reylisted- blac#listed or non?white listed mobile eCuipment is detected

durin an &M2& chec#. The purpose of the tic#et is to lin# the mobile eCuipment under observation with its current user(&M"&). The tic#et also includes information describin when and where the eCuipment was used to enable the trac#in

of such eCuipment. 7inally- if the tic#et was triered by a call attempt- a call reference is provided in order to locate thecorrespondin 1:/.

The &M2& tic#ets are enerated by the M"1 server performin the &M2& chec#.

5.1.3.12 Trigger# 4r $+S-MT-+R, $+S-M>-+R an" $+S-*:-+R +harging:n4rmatin +%%ectin

The 51" 1:/s (51"?MT?1:/- 51"?MO?1:/ and 51"?'&?1:/) are used to collect charin information related tothe 51" features that the P5M' provides in the Pac#et?"witched domain.

These records include details such as /ecord Type- "erved &M"&- "eCuence 'umber etc. The 51" records are enerated

based on the followin trier conditionsD

the 51"?MO?1:/- when the M"1 receives the /'P @5ocation report@ messae from the /'1E

the 51"?MT?1:/- when the M"1 receives the /'P @5ocation report@ messae from the /'1E

the 51"?'&?1:/- when the M"1 receives the /'P @5ocation report@ messae from the /'1.

5.1.3.13 ?S30 'cc!nting

0"3+ is an eample where the servin networ# may use a substantially hiher radio bandwidth than for a standard voicecall. Ihile the invocation of this service- includin the used radio resources- can be captured in the servin M"1 server-

this is not possible in the GM"1 server. >owever- if the inter?networ# accountin is done based on GM"1 1:/s- thisinformation is needed by the GM"1 server in order to provide the reCuired 1:/ information. To that end- the servin

M"1 server can provide this information bac# to the GM"1 server. "ee clause 8.,.*.*.= for further details.

5.1.3.1/ +'M$ +a%% Part 8an"%ing #er7ice

The followin applies to M"1s that are capable of 1M25 1all Party >andlin (1P>)D

7or calls where 1M25 1all Party >andlin (1P>) is involved- one separate record is enerated per call sement. The1M25 1P> service may be applied to oriinatin- forwarded and terminated calls as well as "1P initiated calls.

7or MO- MT and 17 call attempts- the fields related to the incomin le are recorded in the main body. The fieldsrelated to the outoin les of that call sement are recorded in the respective rouped field (1M25 call le

information) per outoin le. ser &nteractions (&) are recorded in a separate rouped field li#e outoin les.

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3#!elease "


22/106

/ecords for sm"17 initiated call attempts differ to MO- MT and 17 records in the followin wayD no le informationshall be recorded in the main body.

Ihere the use of 1P> result in the creation of further call les in one call sement- additional rouped fields shall beadded to the respective 1:/.

Ihere the use of 1P> result in the creation of further call les in a new call sement- a further 1:/ shall be enerated.

1:/ is closed when the last le of the call sement disappeared (moved out- disconnected- etc. ) from the call

sement.

Ihen a call le is moved from one call sement to another- the rouped field for that call le is closed in the respective

1:/ and a new rouped field is opened in the 1:/ of the call sement the call le was moved to.

Ihen the incomin le (recorded in the main body)- is moved from one call sement to another- the rouped field(s) for

the outoin call le(s) isFare alined to reflect the new call constellation.

ser interactions (announcements etc.) are recorded in the 1:/ of the related call sement as a separate rouped field

similar to call les.

The le specific fields listed below shall be recorded in the rouped field $1M25 1all 5e &nformation$ instead of

usin the counterpart in the main body. The counterparts of those fields in the main body are maintained forcompatibility reasons to earlier releases.

? 1M25 :estination 'umber

? Translated 'umber

? 1onnected 'umber

? /oamin 'umber

? Outoin T%GP (in $1M525 1all 5e &nformation$ this item is calledM"1 outoin T%GP)

? dditional 1h. &nfo

? :efault call handlin *

? Gsm"17 address *

? "ervice #ey *

? 7ree format data * (in $1M25 1all 5e &nformation$ this item is called7ree format data incomin *)

? 7ree format data append indicator * (in $1M25 1all 5e &nformation$ this item is called7ree format data append incomin *)

2ditorQs noteD both parameters from the second 71& operation should be clarified- also in the 1:/ table

? 5ocation /outin 'umber (5/')

? 5/' "ource &ndicator

? 5/' uery "tatus &ndicator

? L&P Parameter

? L&P "ource &ndicator

? L&P uery "tatus &ndicator

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3##!elease "


23/106

5.1.3.15 Ser7ice +hange an" a%%acavin received a set?up reCuest from subscriber @@ (,)- M"1? interroates the >5/ of the called subscriber in order

to determine his current location (*). The >5/ shall create an >5/ interroation 1:/.

M"1? routes the call to the M"1 server at which subscriber is currently reistered (3). This terminatin M"1 server(M"1?0) shall create an MT1 record for subscriber @0@. &f M"1? and M"1?0 are co?located- then both the MO1 and

the MT1 records shall be produced in the same M"1 for this call.

The records enerated are subseCuently transferred to the 0illin "ystem of the P5M'.

3

.

8P$M*

TMS+

MS+-'

8$R

?i%%ing

S#tem

?'

.

MS+-?

??

*

.

3

,3

3

.

8P$M*

TMS+TMS+

MS+-'MS+-'

8$R8$R

?i%%ing

S#tem

?i%%ing

S#tem

??'

.

MS+-?MS+-?

???

*

.

3

,3

.igure %$#$$3/ 7o9ile to mo9ile call

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3#,!elease "


28/106

5.2.1./ :ncming ca%% t a raming #!#crier

7iure 8.*.,.= illustrates an incomin call from a fied networ# subscriber @@ to a P5M' subscriber @0@ who iscurrently roamin in another P5M'.

The call is first routed to a GM"1 server (,) and the GM"1 server shall create an incomin ateway record for

accountin purposes as described in clause 8.*.,.*. The GM"1 server interroates the >5/ of the called subscriber inorder to determine his current location (*). The >5/ shall create an &nterroation event record.

The GM"1 server routes the call to the AP5M' in which subscriber @0@ is currently located (3). The GM"1 server

shall create an outoin ateway record for accountin purposes. The GM"1 server shall also create a roamin record.This record includes the &M"& of the @0@ subscriber and may be used as a cross?chec# for the TP information received

from the AP5M'.

The call is then routed by the AP5M' to the M"1 server at which the subscriber is currently located (=). The GM"1

server of the AP5M' shall produce an incomin ateway record and the terminatin M"1 server shall create an MT1record for the call to @0@.

The records enerated are subseCuently transferred to the 0illin "ystem of the appropriate P5M' (). The MT1record enerated by the terminatin M"1 server shall be employed to create the appropriate MT1 TP record. The

TP records shall be included in a TP file and transmitted to the >P5M' (0).

8P$M*

GMS+ 8$R

?i%%ing

S#tem

.

*

3

=

.

VP$M*

GMS+

MS+-??i%%ing

S#tem

??

=

.

,

:S*PST*

,

=

.0

8P$M*

GMS+GMS+ 8$R8$R

?i%%ing

S#tem

?i%%ing

S#tem

.

*

3

=

.

VP$M*

GMS+GMS+

MS+-?MS+-??i%%ing

S#tem

?i%%ing

S#tem

???

=

.

,

:S*PST*

,

=

.0

.igure %$#$$*/ 8ncoming call to a roaming su9scri9er

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3#-!elease "


29/106

5.2.1.5 :ncming ca%% t a P$M* #er7ice centre

7iure 8.*.,.8 illustrates an incomin call from a fied networ# subscriber @@ to a "ervice 1entre directly connected toan M"1 server within a P5M' networ#. 2amples for services provided by such a "ervice 1entre include Aoice Mail

services- Operator services- etc.

The call is routed to a GM"1 server within the P5M' (,). The GM"1 server analyses the dialled diits and routes thecall directly to the M"1 server to which the "ervice 1entre is connected (*).

s >5/ interroation is not reCuired- there will be no >5/ &nterroation record. The GM"1 server shall however-

create an incomin ateway record based on the point at which the call entered the networ# and the destination ("ervice1entre) of the call.

The M"1 server then connects the callin subscriber to the service centre. s no mobile subscriber is involved- theM"1 server will not create an MT1 record- however- the M"1 server shall create a transit record describin the

destination of the call.

The records enerated are subseCuently transferred to the 0illin "ystem of the P5M' ().

&t should be noted that without the transit record- the M"1 server would not enerate a record for this connection.

.

,

:S*PST*

8P$M*

GMS+Tran#it

MS+

?i%%ing

S#tem

,

* Ser7ice

+enter

.

*

.

.

,

:S*PST*

8P$M*

GMS+GMS+Tran#it

MS+

?i%%ing

S#tem

?i%%ing

S#tem

,

* Ser7ice

+enter

Ser7ice

+enter

.

*

.

.igure %$#$$%/ 8ncoming call to a P:74 service centre

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3#"!elease "


30/106

5.2.1.6 +a%% 4rar"ing !ncn"itina%

7iure 8.*.,.9 illustrates an incomin call from a fied networ# subscriber @@ to a mobile subscriber @0@ who hasreistered and activated 1all 7orwardin nconditional (17) for the appropriate service. The call is subseCuently

forwarded to a second fied networ# subscriber @1@.

7or simplicity the reistration and activation of 17 have not been included in the diaram. These actions shall ofcourse be recorded in the appropriate supplementary service records.

The incomin call is routed to a GM"1 server (,). This part of the connection is identical to the scenario outlined in

clause 8.*.,.*.

The GM"1 server interroates the >5/ of the called subscriber in order to determine his current location (*). The >5/

shall create an >5/ interroation 1:/. The >5/ informs the GM"1 server that @0@ has activated 17 to subscriber@1@.

The GM"1 server forwards the call to the fied networ# subscriber @1@ (3). The GM"1 server shall create an MT1record for the @0@ subscriber for the call from @@ and an MO1 (call forwardin) record for the @0@ subscriber for the

call to @1@. 0oth records shall contain the supplementary service employed (17). The GM"1 server shall alsoproduce an outoin ateway record as described in clause 8.*.,.,.

The records enerated are subseCuently transferred to the 0illin "ystem of the >P5M' ().

.

,

:S*PST*

8P$M*

GMS+

MS+

8$R

?i%%ing

S#tem

,

??

.

*

3

1

3

.

,

:S*PST*

8P$M*

GMS+GMS+

MS+MS+

8$R8$R

?i%%ing

S#tem

?i%%ing

S#tem

,

???

.

*

3

1

3

.igure %$#$$+/ Call forwarding unconditional

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33&!elease "


31/106

5.2.1. +a%% 4rar"ing cn"itina% (n !#)

7iure 8.*.,.B illustrates a mobile oriinated call from subscriber @@ to a second mobile subscriber @0@ who hasreistered and activated 1all 7orwardin on 0usy (170) for the appropriate service. The call is subseCuently forwarded

to a third mobile subscriber @1@. &n this eample- all three subscribers are currently located within the same (the home)networ#.

7or simplicity the reistration and activation of 170 have not been included in the diaram.

>avin received a set?up reCuest from subscriber @@ (,)- the oriinatin M"1 server (M"1?) interroates the >5/ of

subscriber @0@ in order to determine his current location (,a). The call is then routed to M"1?0 (*).

M"1? shall create an MO1 record for subscriber @@ containin details of the call to @0@. The >5/ shall produce an

>5/ interroation record.

On determinin that subscriber @0@ is busy and that 170 is active- the forwardin M"1 serverFA5/ (M"1?0)

interroates the >5/ of subscriber @1@ to determine his current location (*a) and forwards the call accordinly (3).

M"1?0 shall produce an MT1 record for the @0@ subscriber for the call from @@ and an MO1 record for the @0@

subscriber for the call to @1@. 0oth records shall include the supplementary service employed (170). The >5/ shall

produce an &nterroation record.

The terminatin M"1 server (M"1?1) shall create a normal MT1 record for subscriber @1@.

The records enerated are subseCuently transferred to the 0illin "ystem of the P5M'.

*

8P$M*

MS+-?

MS+-' 8$R

?'

MS+-+

,

3

??

?+

@!#A

3

*a

,a

*

8P$M*

MS+-?MS+-?

MS+-'MS+-' 8$R8$R

??'

MS+-+MS+-+

,

3

???

??+

@!#A

3

*a

,a

.igure %$#$$,/ Call forwarding conditional (9usy

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33!elease "


32/106

5.2.1.= e%i7er 4 a mi%e terminate" #hrt me##age

7iure 8.*.,.; illustrates the delivery of a short messae to a mobile subscriber.

The short messae service centre delivers the messae to a GM"1 server or ateway function (,). The GM"1 server

shall create an "M" ateway MT record.

The GM"1 server then interroates the >5/ of the subscriber to determine his current location (*). The >5/ shall

create an >5/ interroation record.

The messae is subseCuently transmitted to the M"1 server servin the mobile subscriber and finally to the mobilestation of that subscriber (3). The M"1 server shall create an "M" MT record.

The records enerated are subseCuently transferred to the post?processin system of the >P5M' ().

8P$M*

SMS-

GMS+

MS+-?

8$R

?i%%ing

S#tem

??

.

*

SMS-S+

,

3

.

8P$M*

SMS-

GMS+

MS+-?MS+-?

8$R8$R

?i%%ing

S#tem

?i%%ing

S#tem

???

.

*

SMS-S+SMS-S+

,

3

.

.igure %$#$$-/ 6elivery of a short message to a mo9ile su9scri9er

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33#!elease "


33/106

5.2.1.9 +a%% h%" an" m!%ti-&art #er7ice

7iure 8.*.,.< illustrates the use of the call hold and multi?party services.

mobile subscriber (@@) sets up an outoin call (,) to an &":' subscriber (@0@). This call is recorded as outlined in

clause 8.*.,.,.

"ubscriber @@ then invo#es the call hold service. M"1? shall produce a supplementary service action record for the

invocation.

"ubscriber @@ then sets up a side?call (*) to a second mobile subscriber (@1@) within the same networ#. This call isrecorded as outlined in clause 8.*.,.3.

"ubscriber @@ subseCuently invo#es the multi?party service in order to set up a three?party conference with @0@ and

@1@. M"1? shall produce a common eCuipment record for the use of a conference circuit by subscriber @@. Thisrecord shall record the duration of the whole conference irrespective of the number of parties subseCuently added to- or

removed from the conference connection.

'ote that the MO1 records produced by M"1? for both the ?N 0 and ?N 1 les of the conference shall contain the

supplementary service code for multi?party.

,

.

8P$M*

GMS+

MS+-'?i%%ing

S#tem

?'

.

MS+-+

?+

,*

0

,

:S*PST*

,

*

,

.

8P$M*

GMS+GMS+

MS+-'MS+-'?i%%ing

S#tem

?i%%ing

S#tem

??'

.

MS+-+MS+-+

??+

,*

0

,

:S*PST*

,

*

.igure %$#$$"/ Call hold and multi)party service

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&333!elease "


34/106

5.2.1.10 >!tging ca%% han"%e" +'M$

7iure 8.*.,.,+ illustrates an outoin 1M25 call from a mobile 1M25 subscriber @@ to a fied networ#subscriber @0@ (,).

The @@ subscriber has an active O?1"& (stored in the A5/). Therefore M"1 server? reCuests instructions from the

sm""7 which passes the 1M25 service #ey to the sm"17 to indicate which service loic it should apply (*).

The sm"17 may interroate the >5/ for subscriber information. s a networ# option- the operator may refuse toprovide the reCuested information.

Ihen sm"17 processin is complete the call control is returned to M"1?.

M"1 server? enerates an MO1 record for the @@ subscriber. This record may be lin#ed to an optional "17?record.

The record includes O?1"& data.

The GM"1 server routes the call to the @0@ subscriber (3). The GM"1 server shall create an outoin ateway record

as described in clause 8.*.,.,.

The enerated records are subseCuently transferred to the 0illin "ystem of the >P5M' ().

The followin records are enerated in >P5M' in this call scenario.

Ta9le %$#$$&/ !ecords Generated for an 0utgoing Call andled 9y CA72:

G7SC server 7SC server :!

>!tging gatea recr" M>+ recr" -

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33*!elease "


35/106

:S*PST*

'

MS+-'g#mSS

GMS+g#mSS

g#mS+

?

?i%%ingS#tem

'

1

2

3

>-+S:('-?)

3

8P$M*

8$R

:S*PST*

'

MS+-'g#mSS

GMS+g#mSS

g#mS+

?

?i%%ingS#tem

'

1

2

3

>-+S:('-?)

3

8P$M*

8$R

.igure %$#$$&/ 0utgoing call handled 9y CA72:

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33%!elease "


36/106

5.2.1.11 :ncming ca%% han"%e" +'M$ ith!t re"irectin

7iure 8.*.,.,, illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @0@.

The incomin call is first routed to the GM"1 server (,). The GM"1 server shall create an incomin ateway record for

fied networ# accountin purposes.

The GM"1 server interroates the >5/ of the called subscriber in order to fetch the T?1"& (*). The >5/ shall create an

>5/ interroation record.

The @0@ subscriber has an active T?1"&. Therefore the GM"1 server reCuests instructions from the sm""7 whichpasses the 1M25 service #ey to a sm"17 to indicate which service loic it should apply (3).

The sm"17 may interroate the >5/ for subscriber information. s a networ# option- the operator may refuse to

provide the reCuested information.

Ihen sm"17 processin is complete the call control is returned to the GM"1 server. The GM"1 server shall enerate

a terminatin 1M25 record which contains T?1"& data.

The GM"1 server interroates the >5/ in order to determine his current location (=). The >5/ shall create an >5/

interroation record.

The call is routed to M"1?0 (8). n MT1 record shall be enerated.

7or avoidance of doubt- even if the M"1 server and GM"1 server are co?located both the MT1 and ateway recordsshall be produced.



Ta9le %$#$$/ !ecords Generated for an 8ncoming Call andled 9y CA72: without !e)direction


:ncming gatea recr" MT+ recr" 8$R interrgatin recr"

Terminating +'M$ recr"

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33+!elease "


37/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ingS#tem

'

1

2

5

T-+S:('-?)

3

1

6

/

8$R

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ingS#tem

'

1

2

5

T-+S:('-?)

3

1

6

/

8$R

.igure %$#$$/ 8ncoming call handled 9y CA72: without redirection

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33,!elease "


38/106

5.2.1.12 :ncming ca%% t a raming #!#crier han"%e" +'M$

7iure8.,* illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @0@ who iscurrently roamin in another P5M'.

The call is first routed to a GM"1 server (,) and the GM"1 server shall create an incomin ateway record for fied

networ# accountin purposes.

The GM"1 server interroates the >5/ of the called subscriber in order to fetch the T?1"& (*). The >5/ shall create an>5/ interroation record.

The @0@ subscriber has an active T?1"&. Therefore the GM"1 server reCuests instructions from the sm""7 which

passes the 1M25 service #ey to a sm"17 to indicate which service loic it should apply (3).


Ihen sm"17 processin is complete the call control is returned to the GM"1 server . The GM"1 server shallenerate a terminatin 1M25 record which contains T?1"& data.

The GM"1 server interroates the >5/ in order to determine his current location (=). The >5/ shall create an >5/interroation record.

The GM"1 server routes the call to the AP5M' in which subscriber @0@ is currently located (8). The GM"1 servershall create an outoin ateway record for accountin purposes. The GM"1 server shall also create a roamin record.

This record includes the &M"& of the @0@ subscriber and may be used as a cross?chec# for the TP information receivedfrom the AP5M'.

The call is then routed by the AP5M' to the M"1 server at which the subscriber is currently located (9). The GM"1server of the AP5M' shall produce an incomin ateway record and the terminatin M"1 server shall create an MT1

record for the call to @0@.

The records enerated are subseCuently transferred to the 0illin "ystem of the appropriate P5M' (). The MT1

record enerated by the terminatin M"1 server shall be employed to create the appropriate MT1 TP record. The

TP records shall be included in a TP file and transmitted to the >P5M' (0).


Ta9le %$#$$#$/ !ecords Generated in the P:74 for an8ncoming Call to a !oaming Su9scri9er andled 9y CA72:


:ncming gatea recr" - 8$R interrgatin recr"


Raming recr"

>!tging gatea recr"

The followin records are enerated in AP5M' in this call scenario.

Ta9le %$#$$#$#/ !ecords Generated in the 'P:74 for an8ncoming Call to a !oaming Su9scri9er andled 9y CA72:


:ncming gatea recr" MT+ recr" -

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33-!elease "


39/106

:S*PST*

?

GMS+g#mSS

g#mS+

'

?i%%ingS#tem

'

1

2

5

T-+S:(' -?)

3

1

6

/

GMS+g#mSS

MS+-?g#mSS

?i%%ing

S#tem

g#mS+

5

6

? '

8P$M* VP$M*

8$R

:S*PST*

?

GMS+g#mSS

g#mS+

'

?i%%ingS#tem

'

1

2

5

T-+S:(' -?)

3

1

6

/

GMS+g#mSS

MS+-?g#mSS

?i%%ing

S#tem

g#mS+

5

6

? '

8P$M* VP$M*

8$R

.igure %$#$$#/ 8ncoming call to a roaming su9scri9er handled 9y CA72:

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&33"!elease "


40/106

5.2.1.13 :ncming ca%% han"%e" +'M$ ith re"irectin "eci"e" an" 4rar"ing %eghan"%e" +'M$

7iure 8.*.,.,3 illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @[email protected] call is subseCuently forwarded to a second fied networ# subscriber @1@ by 1M25 initiated 1all 7orwardin.

The incomin call is routed to the GM"1 server (,). The GM"1 server shall create an incomin ateway record forfied networ# accountin purposes.

The GM"1 server interroates the >5/ of the called subscriber in order to fetch the T?1"& and O?1"& (*).





The sm"17 modifies the 1alled Party number and sets the 1P parameter Spply O?1"&$. Ihen sm"17 processin

is complete the call control is returned to the GM"1 server. The GM"1 server shall enerate a terminatin 1M25record which contains T?1"& data.

The @0@ subscriber has an active O?1"&. Therefore the GM"1 server reCuests instructions from the sm""7 whichpasses the 1M25 service #ey to a sm"17 to indicate which service loic it should apply (=).



Ihen sm"17 processin is complete the call control is returned to the GM"1 server.

The GM"1 server redirects the call to the fied networ# subscriber @1@ (8). The GM"1 server shall enerate an MT1

record for the @0@ subscriber for the call from @@ and an MO1 (call forwardin) record for the @0@ subscriber for thecall to @1@. The MO1 record includes O?1"& data and the parameter S1M25 initiated 17 indicator$. The GM"1

server shall also produce an outoin ateway record as described in clause 8.*.,.,.



Ta9le %$#$$3/ !ecords Generated in the 8ncoming Call with!edirection 6ecided and .orwarded :eg andled 9y CA72:




MT+ recr"

M>+ (+) recr"

>!tging gatea recr"

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*&!elease "


41/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ingS#tem

'

1

23

/

T-+S:('-?)>-+S:(?-+)

+

5

1 5

8P$M*

8$R

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ingS#tem

'

1

23

/

T-+S:('-?)>-+S:(?-+)

+

5

1 5

8P$M*

8$R

.igure %$#$$3/ 8ncoming call handled 9y CA72: with redirection decidedand forwarding leg handled 9y CA72:

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*!elease "


42/106


43/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+-'

'

?i%%ing

S#tem

'

1

23

T-+S:('-?)>-+S:(?-+)

/

+

5

1 5

@+U acti7ate"A

8P$M*

8$R

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+-'

'

?i%%ing

S#tem

'

1

23

T-+S:('-?)>-+S:(?-+)

/

+

5

1 5

@+U acti7ate"A

8P$M*

8$R

.igure %$#$$*/ 8ncoming call handled 9y CA72: without redirectionand forwarded early using GS7 SS 9ut controlled 9y CA72:

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*3!elease "


44/106


45/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ing

S#tem

'

1

23

/

T-+S:('-?)>-+S:(?-+)

+

56

1

@+*RB 'cti7ate"A

+a%% attem&t

8P$M*

8$R

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ing

S#tem

'

1

23

/

T-+S:('-?)>-+S:(?-+)

+

56

1

@+*RB 'cti7ate"A

+a%% attem&t

8P$M*

8$R

.igure %$#$$%/ 8ncoming call handled 9y CA72: without redirectionand forwarded late using GS7 SS 9ut controlled 9y CA72:

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*%!elease "


46/106

5.2.1.16 ar% 4rar"e" ca%% cntr%%e" +'M$

7iure 8.*.,.,9 illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @[email protected] call is subseCuently forwarded to a second fied networ# subscriber @1@ by G"M "" 1all 7orwardin

nconditional (17) but controlled by 1M25.

7or simplicity the activation and reistration of 17 have not been included in the diaram. These actions shall ofcourse be reistered in the appropriate supplementary service records.

The incomin call is routed to the GM"1 server (,). The GM"1 server shall create an incomin ateway record for


The GM"1 server interroates the >5/ of the called subscriber in order to fetch the O?1"& (*). The >5/ shall create

an >5/ interroation record. The >5/ informs the GM"1 server that @0@ has activated 17.

The @0@ subscriber has an active O?1"&. 0ecause the @0@ subscriber has activated 17 he acts as the oriinatin party

for the forwarded le. Therefore the GM"1 server reCuests instructions from the sm""7 which passes the 1M25service #ey to a sm"17 to indicate which service loic it should apply (3).



Ihen sm"17 processin is complete the call control is returned to the GM"1 server.

The GM"1 server redirects the call to the fied networ# subscriber @1@ (8). The GM"1 server shall enerate an MT1

record for the @0@ subscriber for the call from @@ and an MO1 (call forwardin) record for the @0@ subscriber for thecall to @1@. The MO1 record includes O?1"& data. The GM"1 server shall also produce an outoin ateway record as

described in clause 8.*.,.,.



Ta9le %$#$$+/ !ecords Generated in the 2arly forwarded call controlled 9y CA72:



MT+ recr"

M>+ (+) recr"

>!tging gatea recr"

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*+!elease "


47/106

:S*PST*

?

MS+-?g# mSS

GMS+g# mSS

g#mS+-'

'

?i%%ing

S#tem

'

1

23

>-+S:(?-+)

+

/

1 /

@+U acti 7ate"A

8P$M*

8$R

:S*PST*

?

MS+-?g# mSS

GMS+g# mSS

g#mS+-'

'

?i%%ing

S#tem

'

1

23

>-+S:(?-+)

+

/

1 /

@+U acti 7ate"A

8P$M*

8$R

.igure %$#$$+/ 2arly forwarded call controlled 9y CA72:

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*,!elease "


48/106

5.2.1.1 $ate 4rar"e" ca%% cntr%%e" +'M$

7iure 8.*.,.,B illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @0@who has reistered and activated 1all 7orwardin on 'o /eply (17'/K) for the appropriate service. The call is

subseCuently forwarded to a second fied networ# subscriber @1@.

7or simplicity the reistration and activation of 17'/K have not been included in this diaram. These actions shall berecorded in the appropriate supplementary service records.



The GM"1 server interroates the >5/ of the called subscriber in order to determine the current location (*). The >5/

shall create an >5/ interroation record.

The call is routed to M"1?0 (3). The @0@ subscriber do not answer the call. M"1?0 shall produce an MT1 record for

the @0@ subscriber for the call from @@.

The @0@ subscriber has an active O?1"&. 0ecause the @0@ subscriber has activated 17'/K he acts as the oriinatin

party for the forwarded le. Therefore M"1?0 reCuests instructions from the sm""7 which passes the 1M25 service

#ey to sm"17?0 to indicate which service loic it should apply (=).


Ihen sm"17 processin is complete the call control is returned to M"1?0.

M"1?0 forwards the call via the GM"1 server to the @1@ subscriber (8). M"1?0 shall produce an MO1 (call

forwardin) for the @0@ subscriber for the call to @1@. The record includes O?1"& data. The GM"1 server shall alsoproduce an outoin ateway record as described in clause 8.*.,.,.



Ta9le %$#$$,/ !ecords Generated in the :ate forwarded call controlled 9y CA72:



>!tging gatea recr" M>+ (+) recr"

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*-!elease "


49/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ing

S#tem

'

1

2

/

3

>-+S:(?-+)

+

5

1 5

@+*RB acti7ate"A

5

+a%% attem&t

8P$M*

8$R

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

?i%%ing

S#tem

'

1

2

/

3

>-+S:(?-+)

+

5

1 5

@+*RB acti7ate"A

5

+a%% attem&t

8P$M*

8$R

.igure %$#$$,/ :ate forwarded call controlled 9y CA72:

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3*"!elease "


50/106

5.2.1.1= :ncming ca%% han"%e" +'M$ ith re"irectin initiate" +'M$ 4eat!re

7iure 8.*.,.,; illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @[email protected] call is subseCuently redirected to a second fied networ# subscriber @1@ by 1M25 initiated redirection.



The GM"1 server interroates the >5/ of the called subscriber in order to fetch the T?1"& (*) and the O?1"& (*). The>5/ shall create an >5/ interroation record.

"ince subscriber @0@ has an active T?1"& and the trier criteria are met the GM"1 server reCuests instructions from

the sm""7 which passes the 1M25 service #ey to a sm"17 to indicate which service loic it should apply (3).

terminatin 1M25 interroation record is enerated in the GM"1 server for invo#in the terminatin 1M25 callhandlin.


The sm"17 returns a modified destination routin address to the GM"1 server (without the option @apply O?1"&@).

Therefore for the redirection le (0?1) the 1M25 feature is not invo#ed.

The GM"1 server redirects the call to the fied networ# subscriber @1@ (=). 7or fied networ# accountin purposes theGM"1 server shall enerate an outoin ateway record as described in clause 8.*.,.,.



Ta9le %$#$$-/ !ecords Generated in the 8ncoming call handled 9y CA72:with redirection initiated 9y CA72: feature


:ncming gatea recr" 8$R interrgatin recr"

Terminating +'M$interrgatin recr"

>!tging gatea recr"

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%&!elease "


51/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+-'

'

?i%%ingS#tem

'

1

23

T-+S:('-?)

+/

1 /

8P$M*

8$R

>-+S:(?-+)

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+-'

'

?i%%ingS#tem

'

1

23

T-+S:('-?)T-+S:('-?)

+/

1 /

8P$M*

8$R

/

1 /

8P$M*

8$R

/

1 /

8P$M*

8$R

1 /

8P$M*

8$R

/

8P$M*

8$R8$R8$R8$R

>-+S:(?-+)>-+S:(?-+)

.igure %$#$$-/ 8ncoming call handled 9y CA72: with redirection initiated and 9y CA72: feature

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%!elease "


52/106

5.2.1.19 +'M$ Scenari 4r Vi#iting Terminatr Trigger +a%%#

7iure 8.*.,.,< illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @0@.

The incomin call is first routed to the GM"1 (,). The GM"1 shall create an incomin ateway record for fied

networ# accountin purposes.

The GM"1 interroates the >5/ (*) of the called subscriber. The >5/ shall create an >5/ interroation record. The

call is routed to M"1?0(3). n MT1 record shall be enerated in M"1?0.

The @0@ subscriber has an active AT?1"& (stored in the A5/). 7or avoidance of doubt in this scenario- the @0@subscriber does not have an active T?1"& in the >5/. Therefore M"1?0 reCuests instructions from the sm""7 which

passes the 1M25 service #ey to the sm"17 to indicate which service loic it should apply (=).


Ihen sm"17 processin is complete the call control is returned to the M"1?0. The M"1?0 shall enerate aterminatin 1M25 (T1/) record which contains AT?1"& data.

The M"1?0 routes the call to the @0@ subscriber (8).

7or avoidance of doubt- even if the M"1 and GM"1 are co?located both the MT1FT1/ and ateway records shall be

produced.

The enerated records are subseCuently transferred to the O" () either as event reports followin the release of the

connection or when collected by the O".


Ta9le %$#$$"/ !ecords Generated for 'isiting Terminating Trigger Calls

G7SC 7SC)5 :!



3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%#!elease "


53/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSS

g#mS+

'

'+?+

'

1

2

5

VT-+S:('-?)

3

1

/

8$R

.igure %$#$$"/ 8ncoming call handled 9y CA72: in 7SC Server without redirection

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%3!elease "


54/106

5.2.1.20 >!tging ca%% han"%e" +'M$ ith ia%%e" +S: Trigger

7iure 8.*.,.*+ illustrates an outoin 1M25 call from a mobile 1M25 subscriber @@ to a fied networ#subscriber @0@ (,).

The @@ subscriber has an active :?1"& (stored in the A5/ and modified 1alled Party number matches :?1"&).

Therefore M"1 server? reCuests instructions from the sm""7 which passes the 1M25 service #ey to the sm"17to indicate which service loic it should apply (*).



Ihen sm"17 processin is complete the call control is returned to M"1?.

M"1 server? enerates an MO1 record for the @@ subscriber which contains :?1"& data. This record may be lin#edto an optional "17?record.

The GM"1 server routes the call to the @0@ subscriber (3). The GM"1 server shall create an outoin ateway recordas described in clause 8.*.,.,.

The enerated records are subseCuently transferred to the post?processin system () either as event reports followinthe release of the connection or when collected by the post?processin system.


Ta9le %$#$$#&/ !ecords Generated for an 0utgoing Call andled 9y CA72:


>!tging gatea recr" M>+ recr" -

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%*!elease "


55/106

:S*PST*

'

MS+-'g#mSS

GMS+g#mSSg#mS+

?

?i%%ingS#tem

'

1

2

3

3

8P$M*

8$R

:S*PST*

'

MS+-'g#mSS

GMS+g#mSSg#mS+

?

?i%%ingS#tem

'

1

2

3

-+S:('-?)

3

8P$M*

8$R

.igure %$#$$#&/ 0utgoing call handled 9y CA72: with 6ialled CS8 Trigger

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%%!elease "


56/106

5.2.1.21 :ncming ca%% han"%e" +'M$ ith re"irectin "eci"e" an" 4rar"ing %eghan"%e" +'M$ ith ia%%e" +S: Trigger

7iure 8.*.,.*, illustrates an incomin call from a fied networ# subscriber @@ to a mobile 1M25 subscriber @[email protected] call is subseCuently forwarded to a second fied networ# subscriber @1@ by 1M25 initiated 1all 7orwardin.

The incomin call is routed to the GM"1 server (,). The GM"1 server shall create an incomin ateway record forfied networ# accountin purposes.

The GM"1 server interroates the >5/ of the called subscriber in order to fetch the T?1"&- O?1"& and :?1"& (*).





The sm"17 modifies the 1alled Party number and sets the 1P parameter Spply O?1"&$. Ihen sm"17 processin

is complete the call control is returned to the GM"1 server. The GM"1 server shall enerate a terminatin 1M25interroation record which contains T?1"& data.

The @0@ subscriber has an active O?1"&. Therefore the GM"1 server reCuests instructions from the sm""7 whichpasses the 1M25 service #ey to a sm"17 to indicate which service loic it should apply (=).



The sm"17 modifies the 1alled Party number. Ihen sm"17 processin is complete the call control is returned to theGM"1 server.

The @0@ subscriber has an active :?1"& (modified 1alled Party number matches :?1"&). Therefore the GM"1 serverreCuests instructions from the sm""7 which passes the 1M25 service #ey to a sm"17 to indicate which service

loic it should apply (8).

The sm"17 may interroate the >5/ for subscriber information. s a networ# option- the operator may refuse toprovide the reCuested information. Ihen sm"17 processin is complete the call control is returned to the GM"1

server.

The GM"1 server redirects the call to the fied networ# subscriber @1@ (9). The GM"1 server shall enerate an MT1record for the @0@ subscriber for the call from @@ and an MO1 (call forwardin) record for the @0@ subscriber for the

call to @1@. The MO1 record includes O?1"& data- the parameter S1M25 initiated 17 indicator$ and :?1"& data. TheGM"1 server shall also produce an outoin ateway record as described in clause 8.*.,.,.

The enerated records are subseCuently transferred to the post?processin system () either as event reports followinthe release of the connection or when collected by the post?processin system.


Ta9le %$#$$#/ !ecords Generated in the 8ncoming Call with!edirection 6ecided and .orwarded :eg andled 9y CA72:




MT+ recr"

M>+ (+) recr"

>!tging gatea recr"

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%+!elease "


57/106

:S*PST*

?

MS+-?g#mSS

GMS+g#mSSg#mS+

'

?i%%ingS#tem

'

1

23

/

T-+S:( -?)>-+S:(?-+)

+5

1 5

8P$M*

8$R

:S*PST*

?

MS+-?g#mSS

GMS+g#mSSg#mS+

'

?i%%ingS#tem

'

1

23

/

T-+S:('-?)

+6

1 6

8P$M*

8$R55

>-+S:(?-+)

-+S:(?-+)

.igure %$#$$#/ 8ncoming call handled 9y CA72: with redirection decidedand forwarding leg handled 9y CA72: with 6ialled CS8 Trigger

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%,!elease "


58/106

5.2.1.22 Mi%e terminate" %catin reC!e#t

7iure 8.*.,.** illustrates eneral networ# positionin for 51" clients eternal to the P5M'.

n eternal 51" client reCuests the current location of a taret 2 from a GM51 (,). &n this release the GM51 shall

not create any 51" record.

The GM51 server then interroates the >5/ of the taret 2 to be located to determine his current location (*). The

>5/ shall create an >5/ interroation record.

The GM51 sends the location service reCuest to the M"1 indicated by the >5/. The M"1 sends a 5ocation /eCuestmessae to /' that initiates the positionin procedure (3). The M"1 shall create an 51"?MT record.

The records enerated are subseCuently transferred to the 0illin "ystem of the P5M' ().

8P$M*

SM

-GMS

MS

-?

8$R

?i%%inS#te

??

.

*

SM

-S+

,

3

.

8P$M*

GM$+

MS

-?MS+

8$R8$R

?i%%inS#te

?i%%ingS#tem

???

.

*

SM

-S+$+Sc%ient

,

3

.

.igure %$#$$##/ 7o9ile terminated location reP5M' in this call scenario.

Ta9le %$#$$#3/ !ecords Generated for an =a>e)up Call andled 9y CA72: CP

7SC :!

M>+ recr" 8$R interrgatin recr"

MT+ recr"

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%-!elease "


59/106

?'

g#mS+

?i%%ingS#tem

22

1

g#mSS

MS+

'

'

8$R

SR

23

22 23

.igure %$#$$#3/ =a>e)up call handled 9y CA72: CP

5.2.1.2/ Three &art cn4erence han"%e" +'M$ +P8

7iure 8.*.,.*= illustrates one eample for establishment of a three party conference via 1M25 1P>..

mobile 1M25 subscriber @@ sets up an outoin call (,) to an &":' subscriber (@0@). This call is recorded asoutlined in clause 8.*.,.,.

sm"17 then invo#es 1P> operation $initiate call attempt$ (*). new call sement (1"*) with an outoin le @1@ iscreated in M"1?.

M"1? interroates the >5/ in order to determine the current location of subscriber @1@ (3). The >5/ shall create aninterroation record.

M"1? initiates set?up of an outoin le towards mobile subscriber @1@ (=). M"1? shall create an MO1 record forthe le towards mobile subscriber @1@. M"1?1 shall create a MT1 record for subscriber @1@.

sm"17 then invo#es 1P> operation $Move5e$ to join all three les in one call sement (8). M"1? shall close theMO1 record for call sement 1"* to outoin le @1@. The MO1 record for the outoin call of the mobile 1M25

subscriber @@ to &":' subscriber @0@ shall be updated to cover the additional outoin 1M25 call le @1@.


Ta9le %$#$$#*/ !ecords Generated for an =a>e)up Call andled 9y CA72: CP

G7SC server 7SC)A 7SC)C :!

!tging gatea recr" M>+ recr" (;';, ;?;, ;+;) MT+ recr" 8$R interrgatin recr"

M>+ recr" (;+;)

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3%"!elease "


60/106

?'

?i%%ingS#tem

22

1

3

g#mSS

MS+-' '

'

/

8$R

MS+-+

?+

:S*PST*

?

1

1

1

GMS+g#mS+

/

25

.igure %$#$$#*/ Three Party Conference handled 9y CA72: CP

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3+&!elease "


61/106

5.2.2 iameter me##age 4%#

'ot applicable- as the separation of the 1T7 and 1:7 is not in the scope of the 1" domain charin standards. /efer toclause =.* for further information.

Aendors may nevertheless implement a separate 1:17 and 117 for 1" domain charin. &n this case- the approach

chosen shall conform to the principles and protocol applications specified in 3GPP T" 3*.* call attemptsFcall modificationsE

"upplementary service actionsE

>5/ interroationE

5ocation updatin (>5/ and A5/)E

"hort messae service (point?to?point)- mobile oriinatedE

"hort messae service (point?to?point)- mobile terminatedE

"hort messae service (point?to?point)- mobile oriinated interwor#in M"1 serverE

"hort messae service (point?to?point)- mobile terminated ateway M"1 serverE

1ommon eCuipment usaeE

Mobile terminated location reCuestE

Mobile oriinated location reCuestE

'etwor# induced location reCuest.

more detailed description of the records is found in clause 9.,. The detailed formal description of the data defined inthe present document is to be found in 3GPP T" 3*.*


62/106

5.2./ GTPD recr" tran#4er 4%#

'ot applicable- as the separation of the 1:7 and 1G7 is not in the scope of the 1" domain charin standards. /efer to

clause =.* for further information.

Aendors may nevertheless implement a separate 117 and 1G7 for 1" domain charin. &n this case- the approach

chosen shall conform to the principles and protocol applications specified in 3GPP T" 3*.*


63/106

6 e4initin 4 charging in4rmatin

This clause provides "tae 3 specifications of the 1:/ type and content for the 3GPP 1" domain. 7or each of the 1:/types listed in clause 8.*.3- a parameter table- which ives a short description of the parameters- is provided. The

detailed specification of the 1:/ parameters and their encodin is contained in 3GPP T" 3*.*owever- since 1:/ processin and transport consume networ# resources-operators may opt to eliminate some of the parameters that are not essential for their operation. This operator

provisionable reduction is specified by the parameter cateory.

parameter cateory can have one of two primary valuesD

M This parameter is Mandatory and shall always be present in the 1:/E

C This parameter shall be present in the 1:/ only when certain 1onditions are met. These 1onditions are

specified as part of the parameter definition.

"ome of these parameters are desinated as Operator (!) provisionable. sin TM' manaement functions or specific

tools provided by an eCuipment vendor- operators may choose- if they wish- to include or omit the parameter from the

1:/. Once omitted- this parameter is not enerated in a 1:/. To avoid any potential ambiuity- a 1:/ eneratinelement M"T be able to provide all these parameters. Only an operator can choose whether or not these parameters

should be enerated in its system.

Those parameters that the operator may confiure to be present or absent are further Cualified with the @Operator

provisionable@ indicator as followsD

!M This is a parameter that- if provisioned by the operator to be present- shall always be included in the 1:/s.&n other words- a OMparameter that is provisioned to be present is a mandatory parameterE

!C This is a parameter that- if provisioned by the operator to be present- shall be included in the 1:/s when the

reCuired conditions are met. &n other words- a O1parameter that is confiured to be present is a conditionalparameter.

The 1" nodes shall be able to provide the 1:/s at the 0illin "ystem interface in the format and content described in

the present document. dditional 1:/ formats and contents- enerated by the 1" nodes- may be available at theinterface to the billin system to meet the reCuirements of the billin system- these are outside of the scope of 3GPP

standardi!ation.

The followin tables provide a brief description of each 1:/ parameter. 7ull definitions of the parameters- sorted bythe parameter name in alphabetical order- are provided in 3GPP T" 3*.*


64/106

6.1.3.1 Mi%e riginate" ca%% attem&t

&f the eneration of these records is enabled then an MO1 record shall be created for each outoin call attempt madeby a mobile station. These MO1 records shall be produced in the oriinatin M"1.

Ta9le +$$3$/ 70C record

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3+*!elease "


65/106

.ield #G 3G 6escription

Recr" T&e M M Mi%e riginate".

Ser7e" :MS: M M :MS: 4 the ca%%ing &art.

Ser7e" :M: + + :M: 4 the ca%%ing M, i4 a7ai%a%e.

Ser7e" MS:S* >M >M The &rimar MS:S* 4 the ca%%ing &art.

+a%%e" *!mer M M The a""re## 4 the ca%%e" &art i.e. the n!mer "ia%%e" the ca%%ing #!#crier.

Tran#%ate"*!mer

>+ >+ The ca%%e" n!mer a4ter "igit tran#%atin ithin the MS+ (i4 a&&%ica%e)

+nnecte"*!mer

>+ >+ The n!mer 4 the cnnecte" &art i4 "i44erent t the +a%%e" *!mer

Raming *!mer >+ >+ The Mi%e Statin Raming *!mer em&%e" t r!te thi# cnnectin, i4 a&&%ica%e.

Recr"ing ntit M M The .16/ n!mer 4 the 7i#ite" MS+ &r"!cing the recr".

:ncming TEGP >M >+ The MS+ tr!n< gr!& n hich the ca%% riginate" , !#!a%% 4rm the ?SS. :4 a7ai%a%e in3G, thi# &arameter #ha%% e #!&&%ie".

>!tging TEGP >M >+ The tr!n< gr!& n hich the ca%% %e4t the MS+. :4 a7ai%a%e in 3G, thi# &arameter #ha%% e#!&&%ie".

$catin M M The i"entit 4 the ce%% r the S'+ at the time 4 +R creatin, inc%!"ing the %catin areac"e an" M++M*+.

+hange 4$catin

>+ >+ ' %i#t 4 change# in $catin 'rea +"e Ser7ice 'rea +"e +e%% :" an" M++M*+.ach time-#tam&e".

?a#ic #er7ice M M ?earer r te%e#er7ice em&%e".Rate :n"icatin >+ >+ Pre#ent i4 ;rate a"a&tin; &arameter# 4r the a#ic #er7ice ere #igna%%e" eteen the

MSU an" the netr+ &arameter# #ent t the MS e.g. a# a re#!%t 4 a tari44 #itch 7er, inc%!"ing thetime at hich the ne #et a# a&&%ie". Thi# 4ie%" #ha%% e #!&&%ie" n% hen '+&arameter# ha7e een #ent.

MS +%a##mar< M M The mi%e #tatin c%a##mar< em&%e" n ca%% #et-!&.+hange 4+%a##mar+ >+ ' %i#t 4 change# t the c%a##mar< "!ring the cnnectin each time-#tam&e"

7ent time#tam

++>M

++>M

SeiH!re time time 4 incming tra44ic channe% #eiH!re (4r !n#!cce##4!% ca%% attem&t#)'n#er time 4 an#er (4r #!cce##4!% ca%%#)Re%ea#e time time 4 tra44ic channe% re%ea#e

+a%% "!ratin M M The chargea%e "!ratin 4 the cnnectin 4r #!cce##4!% ca%%#, the h%"ing time 4r ca%%attem&t#.

ata 7%!me + - The n!mer 4 "ata #egment# tran#mitte" i4 a7ai%a%e at the MS+

Ra"i +han.ReC!e#te"

>M - The t&e 4 ra"i tra44ic channe% (4!%% ha%4 etc.) reC!e#te" the MS.

Ra"i +han. U#e" M - The t&e 4 ra"i channe% act!a%% !#e" (4!%% r ha%4 rate).

+hange 4 Ra".+han.

>+ - ' %i#t 4 change# each time #tam&e"

+a!#e 4rterminatin

M M The rea#n 4r the re%ea#e 4 the cnnectin.

iagn#tic# >M >M ' mre "etai%e" rea#n 4r the re%ea#e 4 the cnnectin.

+a%% re4erence M M ' %ca% i"enti4ier "i#ting!i#hing eteen tran#actin# n the #ame MS

SeC!ence n. + + Partia% recr" #eC!ence n!mer, n% &re#ent in ca#e 4 &artia% recr"#.

'""itina% +hg.:n4

>+ >+ +hargen charge in"icatr an" a""itina% charging &arameter#, hen a7ai%a%e.

Recr" eten#in# >+ >+ ' #et 4 netr< man!4act!rer #&eci4ic eten#in# t the recr", hen a7ai%a%e.

G#mS+ a""re## + + :"enti4ie# the +'M$ #er7er #er7ing the #!#crier. Sha%% e &re#ent n% i4 +'M$ i#a&&%ie".

Ser7ice


66/106


*!mer 4 8S+S+hanne%#ReC!e#te"

+ - The maim!m n!mer 4 8S+S channe%# reC!e#te" a# recei7e" 4rm the MS at ca%% #et-!&. Sha%% n% e &re#ent 4r 8S+S cnnectin#.

*!mer 4 8S+S+hanne%#'%%cate"

+ - The n!mer 4 8S+S channe%# a%%cate" t the MS at ca%% #et-!&. Sha%% n% e &re#ent4r 8S+S cnnectin#.

+hange 4 8S+SParameter#

+ - ' %i#t 4 netr< r !#er initiate" change# 4 n!mer 4 8S+S channe%# "!ring acnnectin each time-#tam&e". Sha%% n% e &re#ent in ca#e 4 an 8S+S ca%%, i4 thea#ic 8S+S &arameter# are m"i4ie" "!e the !#er r netr< initiate" m"i4icatin&rce"!re.

ie" *etr+ >+ :n"icate# the !#er "ata rate a&&%ie" 4r the cnnectin in the 4ie" netrc e#crie# the it-rate the UMTS earer #er7ice #ha%% g!arantee t the !#er r a&&%icatin.G!arantee" ?it Rate ma e !#e" t 4aci%itate a"mi##in cntr% a#e" n a7ai%a%e

re#!rce#, an" 4r re#!rce a%%catin ithin UMTS. Sha%% n% e &re#ent 4r UMTS "atacnnectin#.

Maim!m it rate - >c Maim!m ?it Rate can e !#e" t ma


67/106


J:P S!rce:n"icatr

- >+ J:P S!rce :n"icatr te%%# the #!rce 4 the J:P

J:P I!er Stat!#:n"icatr

- >+ Stat!# 4 *!mer Prtai%it C!er.

Partia% Recr"T&e

>+ >+ :n"icate# the e7ent (time %imit etc.) that ca!#e" the generatin 4 a &artia% recr".

Rea#n 4r #er7icechange

- >+ :n"icate# the t&e 4 #er7ice change an" 4a%%ac+ :n"icate# the #er7ice change initiatr.

Re"ia% 'ttem&t >+ >+ :n"icate# t the netr< that a ca%% i# the re#!%t 4 a re"ia% attem&t t #itch 4rm #&eech tm!%time"ia r 7ice-7er#a

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3+,!elease "


68/106


69/106


70/106

6.1.3.3 Mi%e riginate" ca%% 4rar"ing attem&t

&f the eneration of MO1 records is enabled in the forwardin M"1 then the forwardin M"1 shall produce an MO1record for the forwarded?le of the call.

Ta9le +$$3$3/ 70C1 call forwarding record

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3,&!elease "


71/106


Recr" T&e M M Mi%e riginate".

Ser7e" :MS: M M :MS: 4 the ca%%ing &art.

Ser7e" MS:S* >M >M The MS:S* 4 the 4rar"ing &art.

+a%%ing *!mer >c >c The a""re## 4 the ca%%ing &art.

+a%%e" *!mer M M The a""re## 4 the ;4rar"e"-t; &art.

Tran#%ate"*!mer

>+ >+ The ca%%e" n!mer a4ter "igit tran#%atin ithin the MS+ (i4 a&&%ica%e)

+nnecte"*!mer

>+ >+ The n!mer 4 the cnnecte" &art i4 "i44erent t the +a%%e" *!mer

Raming *!mer >+ >+ The Mi%e Statin Raming *!mer em&%e" t r!te thi# cnnectin,i4 a&&%ica%e.

Recr"ing ntit M M The .16/ n!mer 4 the 4rar"ing MS+

:ncming TEGP >M >M The MS+ tr!n< gr!& n hich the ca%% riginate" at the 4rar"ing MS+.

>!tging TEGP >M >M The tr!n< gr!& n hich the ca%% %e4t the 4rar"ing MS+

?a#ic #er7ice + + ?earer r te%e#er7ice em&%e", nt a%a# a7ai%a%e e.g. in ca#e 4 ca%% 4rar"ing!ncn"itina%.

Rate '"a&tatin >+ >+ Pre#ent i4 ;rate a"a&tin; &arameter# 4r the a#ic #er7ice ere #igna%%e" eteen theMSU an" the netr+ >+ :n"icate# the !#er "ata rate a&&%ie" 4r the cnnectin in the 4ie" netr4Ser7ice

>+ >+ ' %i#t 4 change# 4 a#ic #er7ice "!ring a cnnectin each time-#tam&e".

S!&&%ementarSer7ice#

+ + S!&&%ementar #er7ice# in7M >M ' mre "etai%e" rea#n 4r the re%ea#e 4 the cnnectin.

+a%% re4erence M M ' %ca% i"enti4ier "i#ting!i#hing eteen tran#actin# n the #ame MS

SeC!ence n. + + Partia% recr" #eC!ence n!mer, n% &re#ent in ca#e 4 &artia% recr"#.

'""itina% +hg.:n4

>+ > +hargen charge in"icatr an" a""itina% charging &arameter#, hen a7ai%a%e.

Recr"eten#in#

>+ >+ ' #et 4 netr+ >+ :n"icate# hether r nt a +'M$ ca%% enc!ntere" "e4a!%t ca%% han"%ing. Thi# 4ie%" #ha%% e&re#ent n% i4 "e4a!%t ca%% han"%ing ha# een a&&%ie".

*!mer 4 Penc!ntere"

>+ >+ *!mer that c!nt# h 4ten arme" "etectin &int# (TP an" P) ere enc!ntere".Sha%% e &re#ent n% i4 +'M$ i# a&&%ie".

$e7e% 4 +'M$#er7ice

>+ >+ :n"icatr 4 the cm&%eit 4 the +'M$ 4eat!re !#e". Sha%% e &re#ent n% i4 +'M$ i#a&&%ie".

ree 4rmat ata + + Thi# 4ie%" cntain# "ata #ent the g#mS+ in the !rni#h +harging :n4rmatin (+:)me##age#. The "ata can e #ent either in ne +: me##age r #e7era% +: me##age# ith

a&&en" in"icatr. Sha%% e &re#ent n% i4 +'M$ i# a&&%ie".+'M$ ca%% %egin4rmatin

+ + Set 4 +'M$ in4rmatin :#. ach 4 the#e :# cntain# in4rmatin re%ate" t ne!tging +'M$ ca%% %eg. Sha%% e &re#ent n% i4 +'M$ i# a&&%ie".

3GPP

3GPP TS 3#$#%& '"$$& (#&&)&3,!elease "


72/106


ree 4rmat "ataa&&en" in"icatr

+ + :n"icatr i4 4ree 4rmat "ata 4rm thi# +R i# t e a&&en"e" t 4ree 4rmat "ata in &re7i!#&artia% +R. Sha%% e &am

Documents

Basic Call Scenario