Unheirarchy
Error
Unheirarchy
False
Unheirarchy
True
start:Null
Compare
=
<
Error
>
Control flow:
(a) Control
λ λ
Unheirarchy Error Unheirarchy
False Unheirarchy
True
type: x. y.if(x=y, if(y=<_,_>, equal,
greater, less)) value:nil compare:list list
true false error
start:Null Compare
exit:true
exit:false
exit:error
Data:
(b) Data
Figure 12.2: Null hierarchicalSIB
12.4 GET N
The Get N hierarchical SIB queries the user for information which the user has
“N” tries to supply. The data supplied by the user is verified to see that it has the correct format. Should the data supplied by the user not conform to the required format he is queried once more, until he runs out of tries. This hierarchical SIB exemplifies how normal constructs, such as in this case getting additional infor-mation from the user, can be encapsulated using the hierarchicalSIB concept.
Input
Logical Start
Service Support Data
- type The type of information to be collected from the user.
- length The length of the data to be collected from the user.
- format The format expected of the data collected from the user.
- ask The message informing the user what is expected of him.
- wrong The message informing the user that the data supplied by the user was incorrect.
- end The message informing the user that he is not given any more tries to supply the requested data.
- errormsg The message informing the user that a internal error has occurred within the service and that the service will be aborted.
- no of tries The maximal number of tries allowed the user to supply the requested data.
- CIDFP-tries The place in which it is recorded the number of tries the user has made to supply the requested data.
- CIDFP-collected The place in which the information supplied by the user is to be stored.
- success TheSIBto which the control will be returned to when returning on the Success logical end.
- fail TheSIBto which the control will be returned to when returning on the Fail logical end.
- error The SIB to which the control will be returned to when returning on the Error logical end.
Call Instance Data
- tries The number of tries the user has made to supply the requested inform-ing.
Output Logical End
- Success - Fail - Error
Call Instance Data
- collected The information supplied by the user.
The Get N SIBs defined graphically in Figure 12.4 and the graphical notation for it in Figure 12.3.
Start
CID
Error
CID Name
[Get_N]
Success Fail
Figure 12.3: Get N HSIB
12.4 Get N 141
Unheirachy Fail Error
Input Verify
Success
Retry Error Error
Error Success
Success
Success Fail
Pass
Algorithm
Algorithm User Interaction
Unheirachy Verify
RetryTest
RetryFail Error
Success
>
=<
Success
User Interaction Retry Announce User Interaction Compare
User Interaction Success
Unheirachy
ErrorMsg Error
start:Get_N
Control flow:
(a) Control
tries no_of_tries ask type length format collected
wrong end errormsg success fail error
λ λ
λ λ
collected
Unheirachy type: x. y.(x + y) Fail
Input Verify
Success
Retry Algorithm
Algorithm User Interaction
Unheirachy Verify
RetryTest
RetryFail User Interaction Retry Announce User Interaction Compare
User Interaction Unheirachy
ErrorMsg Error
start:Get_N
exit:error exit:fail exit:success
type:null announcement:wrong
type:null
type:null announcement:error announcement:end compare:< ,no_of_tries>
type: z. <x,y>.(x < y) value:no_of_tries data:
min:length max:length format:format announcement:ask
type:type min:length max:length
algorithm:tries value:0 type: x. y.0
Data:
identifier: collected:
identifier:
algorithm:
(b) Data
Figure 12.4: Get N hierarchical SIB
Get N = {
hstart : Get N, halgorithm,
{htype, himmediate, λx.λx.0ii, hvalue, himmediate, 0ii,
hcidfp−algorithm, hparameter, triesii, hcidfp−identifier, hparameter, triesii, hsuccess, himmediate, Inputii, herror, himmediate, Errorii}ii,
hInput, hui,
{hannoucement, hparameter, askii, htype, hparameter, typeii, hmin, hparameter, lengthii, hmax, hparameter, lengthii, hcollected, hparameter, collectedii,
hsuccess, himmediate, Verifyii, herror, himmediate, Retryii}ii, hVerify,
hverify,
{hmin, hparameter, lengthii, hmax, hparameter, lengthii,
hformat, hparameter, formatii, hcidfp−data, hparameter, collectedii,
hpass, himmediate, Successii, hfail, himmediate, Retryii, herror, himmediate, Errorii}ii, hRetry,
halgorithm,
{htype, himmediate, λx.λy.x + yii, hvalue, himmediate, 1ii,
hcidfp−algorithm, hparameter, triesii, hcidfp−identifier, hparameter, triesii, hsuccess, himmediate, RetryTestii, herror, himmediate, Errorii}ii, hRetryTest,
hcompare,
{htype, himmediate, λzλhx, yi.x < yii, hvalue, hparameter, no of triesii, hcidfp−compare, hcons, hhparameter, triesi, hparameter, no of triesiiii, hgreater, himmediate, RetryAnnounceii, hless, himmediate, RetryFailii, hequal, himmediate, RetryFailii, herror, himmediate, Errorii}ii, hRetryAnnounce,
hui,
{hannoucement, hparameter, wrongii, htype, himmediate, nullii, hsuccess, himmediate, Inputii}ii,
hRetryFail, hui,
{hannoucement, hparameter, endii, htype, himmediate, nullii, hsuccess, himmediate, Failii}ii,
hErrorMsg, hui,
{hannoucement, hparameter, errormsgii, htype, himmediate, nullii, hsuccess, himmediate, Errorii}ii,
hSuccess, hunhierarchy,
{hexit, hparameter, successii}ii, hFail,
hunhierarchy,
{hexit, hparameter, failii}ii, hError,
hunhierarchy,
{hexit, hparameter, errorii}ii, }
Part IV
Services
Chapter 13
Introduction
The services and service features are presented as sequences of SIBs in graphical form as described in Section 1.5.1. The services and service are also presented in textual form. Further the constants defining the initiation points and the what the name is of theSIB chain defining the service.
All in all three service features are and three services are presented.
Two service features concern the billing of normal call handling which we have chosen to break out of the call handling and make into service features since they does not seems a natural integral part of call control. We feel that the model becomes simpler and less ad hoc when the billing is realised as separate features, one adding costs to the call and the other charging the accounts when the call is completed. This is of course, by necessity, a much simplified view of the charging system.
13.1 CONSTANTS
The “Billing DPs” are the points in a call where billing is to occur.
Billing DPs def= {Route Select Failure, O Call Party Busy, O No Answer, O Disconnect, O Abandon,
T Call Party Busy, T No Answer, T Disconnect, T Abandon}
The “standard profile” is definition of active and subscribed services the are as-sumed for all user by default, and the actual profile of a subscriber is gained by overriding these defaults.
The default service subscription consists of normal charging service that sets up the call so that normal billing takes place. The normal billing service that for each user noted as payer exacts it share of the cost for the call.
standard profile def= hNormal Charging armed ∪ Normal Billing armed, Normal Charging present ∪ Normal Billing present, Normal Charging lookup ∪ Normal Billing lookupi
Chapter 14
Service Features
14.1 DOMAINS
ServiceFeature ≡ {Normal Billing, Normal Charging, CF}