Hlr04r2a

Features and Services in HLR 10

Chapter 4

This chapter is designed to provide the student with knowledgeof services and features in HLR 10.

OBJECTIVES:Upon completion of this chapter the student will be able to:

• Handle Supplementary Services Implementation

• Define conditional and unconditional call forwarding

• Describe the different types of call barring

• Handle Short Message services implementation

• Describe Flexible Numbering

• Describe the role of HLR in data calls

GSM HLR 10 Operation and Maintenance

– 2 – EN/LZT 123 3972 R2A

ll aa nn kkBB

iioonnaall llyy

ttnneettnnII

4 Features and Services in HLR 10

EN/LZT 123 3972 R2A – 71 –


Table of Contents

Topic Page

SUPPLEMENTARY SERVICES IMPLEMENTATION .........................73

SUPPLEMENTARY SERVICE SUBSCRIBER PROCEDURES...........75

REMOTE SUBSCRIBER PROCEDURE MECHANISM .......................79

CALL FORWARDING SERVICES.......................................................81

CALL FORWARDING UNCONDITIONAL (CFU) .................................82

CONDITIONAL CALL FORWARD........................................................83

DEFAULT CALL FORWARDING (DCF)...............................................84

MONITORING OF CALL FORWARDING REGISTRATION.................85

7-DIGIT DIALING .................................................................................86

CALL BARRING SERVICES ...............................................................90

OPERATOR DETERMINED BARRING ...............................................90

OPERATOR DETERMINED BARRING IN HLR FOR INTER-ZONALCALLS ..................................................................................................92

OPERATOR DETERMINED BARRING IN HLR FOR CALLFORWARDED-TO NUMBER ...............................................................92

ERICSSON PROPRIETARY SERVICES.............................................94

SHORT MESSAGE SERVICES...........................................................95

MOBILE TERMINATED SHORT MESSAGE SERVICESUBSCRIPTION...................................................................................95

SHORT MESSAGE ROAMING ROUTING...........................................95

SET MESSAGE WAITING DATA.........................................................96

NOTE MS PRESENT ...........................................................................96

SHORT MESSAGE ALERT..................................................................97

HIGH PENETRATION NOTIFICATION................................................97

HLR SHORT MESSAGE SERVICE CENTER......................................97


– 72 – EN/LZT 123 3972 R2A

FLEXIBLE NUMBERING .....................................................................99

DATA CALLS IN HLR........................................................................104

BEARER CAPABILITIES....................................................................104

BEARER CAPABILITY ADMINISTRATION .......................................104

MULTIPLE NUMBERING SCHEME...................................................106

SINGLE NUMBERING SCHEME .......................................................107

ISDN ORIGINATING DATA CALL......................................................109

HIGH SPEED CIRCUIT SWITCHED DATA (HSCSD) IN HLR...........110


EN/LZT 123 3972 R2A – 73 –

SUPPLEMENTARY SERVICES IMPLEMENTATION

The command HGSSI is used to register and/or activate asupplementary service for a mobile subscriber. The registrationand activation of the supplementary service applies to the BasicService Group specified in the command, or to all applicableBasic Service Groups which have individual Basic servicessubscribed to, if the BSG is not given in the command.

A supplementary service, e.g. Call Forwarding or Barring, couldeither be activated from the MS or by the operator. Thecommand HGSSI handles the operator-controlled activation of aservice.

EXAMPLES :

HGSSI:MSISDN=3415100004,SS=CFNRY, FNUM=15895800,OFA=1, TIME=15;

Call Forwarding on No ReplY (CFNRY) is registered, with thenumber 15895800 as forwarded-to number 1, as origin forforwarded-to number analysis. The no reply condition timer isequal to 15 seconds. The subscription of MSISDN 3415100004are all the basic service groups in the subscription.

Parameter FNUM will only be accepted when the command isintended to register a call forwarding service.

When parameter OFA is required, and has not been specified inthe command, a value assigned as default to the mobilesubscriber is used.

HGSSI: MSISDN=3415100004, SS=CFB, BSG=TS10,FNUM=15895845, SADD=0-1A3C;

Call Forwarding on MS Busy (CFB) is registered for thesubscription of MSISDN 3415100004 with the number15895845 as forwarded-to number; sub-address type NSAP andthe sub-address 1A3C is for the ‘speech transmission’ basicservice group.

When registering a call forwarding service, if parameter SADDhas been specified the forwarded-to subaddress is tied to theforwarded-to number.


– 74 – EN/LZT 123 3972 R2A

HGSSI:MSISDN=3415100004, SS=BAIC;

Barring of All Incoming Calls (BAIC) is activated for thesubscription which MSISDN is 3415100004 are all the basicservice groups in the subscription.

HGSSE:MSISDN=3415100004, SS=CFB;

Call Forwarding on MS Busy (CFB) is erased for thesubscription MSISDN at 3415100004, which is all the basicservices groups in the subscription. This means that theforwarded-to number is deleted.

Depending on the supplementary service specified, someoptional parameters are required and some are not. SeeApplication Information for block HTRAN.

These Supplementary Services are not used in the commandsHGSSI and HGSSE:

• AOC (Advice Of Charge)

• CLIP (Calling Line Identification Presentation)

• CLIR (Calling Line Identification Restriction)

• COLP (COnnected Line identification Presentation)

• COLR (COnnected Line identification Restriction)

• CUG (Closed User Group)

• HOLD (Call Hold)

• ICI (Immediate Call Itemization)

• MPTY (MultiParTY service)

• OIN (Originating Intelligent Network)

• TIN (Terminating Intelligent Network)

• OICK (Originating Intelligent network Category Key)

• TICK (Terminating Intelligent network Category Key)

OPI: HLR Mobile Subscriber Supplementary Service Register

OPI: HLR Mobile Subscriber Supplementary Service Erase

OPI: HLR Mobile Subscriber Supplementary Service Activate

OPI: HLR Mobile Subscriber Supplementary Service Deactivate


EN/LZT 123 3972 R2A – 75 –

SUPPLEMENTARY SERVICE SUBSCRIBER PROCEDURES

This function provides the mobile subscriber with the means toregister, erase, activate, deactivate, and interrogate SS whichhave been provided to the subscriber. It also provides thesubscriber with the possibility to register a new password.

When a mobile subscriber wants to change a supplementaryservice, e.g. call forwarding unconditional, the subscriber mustrequest a signaling channel and invoke a change in HLR.

SS-Request

SS-Confirm

Supplementaryservice ack

Supplementaryservice ack

Operator SupplementaryService

Operator SupplementaryService

Figure 4-1 Invocation of a SS service procedure

The MS sends an SS-request to the MSC which passes it ontothe VLR. The VLR will then update itself and update the HLR.From the HLR an acknowledgment is sent to the VLR and VLRacknowledges to the MS.

Supplementary Services Control

The MS shall support the Man-Machine Interface (MMI)procedure specified as:

Activation: *SC*SI#Deactivation: #SC*SI#Interrogation: *#SC*SI#Registration: *SC*SI# and **SC*SI#Erasure: ##SC*SI#

This structure consists of the following parts:• Service Code, SC (2 or 3 digits)• Supplementary Information, SI (variable length)


– 76 – EN/LZT 123 3972 R2A

The procedure always starts with *, #, ## or *# and is finishedby #. Each part within the procedure is separated by *.

The service code uniquely specifies the Supplementary Service,either as a defined GSM Supplementary Service or as a spareservice code. All spare services codes shall be reserved forfuture use.

The MS shall determine from the context whether an entry of asingle *, activation or registration was intended. E.g. a callforwarding request with a single * would be interpreted as aregistration, if containing a forwarded-to number or anactivation if it does not contain a forwarded-to number.

5HJLVWUDWLRQ�RI�QHZ�SDVVZRUG

The following procedure permits the user to change thepassword relating to use of Supplementary Services. Thepassword may not be erased or interrogated. The procedure is asfollows:

*03*ZZ*OLD_PASSW*NEW_PASSWORD*NEW_PASS#

For Barring Services, ZZ= 330;

3UHVHQWDWLRQ�RI�,0(,

The following procedure shall instruct the ME to display itsIMEI:

*# 06 #


EN/LZT 123 3972 R2A – 77 –

2WKHU�&RGHV�IRU�'HILQHG�6XSSOHPHQWDU\�6HUYLFHV

6XSSOHPHQWDU\�6HUYLFH 6HUYLFH�&RGH

eMLPP 75 and 75n

CD 66

CLIP 30

CLIR 31

COLP 76

COLR 77

CFU 21

CF Busy 67

CF No Reply 61

CF Not Reachable 62

all CF 002

all conditional CF 004

WAIT 43

UUS Service 1 361

UUS Service 2 362

UUS Service 3 363

all UUS Services 360

BAOC 33

BAOIC 331

BAOIC exc home 332

BAIC 35

BAIC roaming 351

all Barring Serv. 330

Outg.Barr.Serv. 333

Inc. Barring Serv. 353


– 78 – EN/LZT 123 3972 R2A

EXAMPLE OF MOBILE INITIATED ACTIVATION OF CALLFORWARDING SERVICE

Before the Call Forwarding activation is accepted, checks aremade on the forward-to-number ensuring that it is in theinternational format and that the number is not restricted. If thenumber is not in an international format, then the activationshould be converted in the CF analysis.

HLR

MSC/VLR

BSC

BSSAP

MAP

BTSLAPD

Signaling pathTraffic path

MS1

2

3

Figure 4-2 Activation of Call Forwarding from MS

1. The subscriber wishes to activate unconditional callforwarding. This can be done from the menu or by dialing �� .

2. The MS will generate the message and send it to the HLRwhere its subscription is held.

3. The HLR will check the C-number in an analysis table. Notethat the C-number sent, is in an unknown format. Before theC-number can be stored, and the MS informed, the numbermust be converted into the international format, by removingthe 0 and inserting the country code.


EN/LZT 123 3972 R2A – 79 –

The three conditional call forward services have the followingcodes:

�� call forward when not reachable

�� call forward on no reply

�� call forward on busy

REMOTE SUBSCRIBER PROCEDURE MECHANISM

This feature enables the HLR to receive the standardsupplementary services (SS) operations (e.g. invoke a callforwarding) from an external node, and not only from the VLRor by command. The implementation is entirely in the HLR;however, an external node is needed in order to take advantageof the feature and provide a service to the end-user.

By introducing a mechanism which correctly handles externalSS operations addressed via MSISDN (since the subscriber’sIMSI may not be available in the external node), a subscriptionmay be updated regardless of whether an MS is reachable or notreachable.

The external node must use the MAP interface to take access tothe HLR. The following MAP V2 messages are accepted fromthe external node:

• ActivateSS

• DeactivateSS

• RegisterSS

• EraseSS

• InterrogateSS

• RegisterPassword

• Process UnstructuredSS-Request


– 80 – EN/LZT 123 3972 R2A

DTMF

Register Fwd-to number

PSTN/ISDN

Internet

Register Fwd-to number

WWW browser

externalNode

MAP V2

HLR

Figure 4-3 Remote Subscriber Procedure


EN/LZT 123 3972 R2A – 81 –

CALL FORWARDING SERVICES

Call Forwarding allows the Mobile Subscriber to have theirincoming calls forwarded to another directory number. The callscan be forwarded in the following situations:

• Call Forwarding on MS Not ReaChable (CFNRC)

• Call Forwarding on MS Busy (CFB)

• Call Forwarding on No ReplY (CFNRY)

• Call Forwarding Unconditional (CFU)

The HLR orders the GMSC to reroute a terminating call whenthe mobile subscriber is not reachable or when unconditionalcall forwarding is active. If inactive, the call is handled as anormal terminating call in the HLR.

In addition, the calling subscriber may be given notificationdepending on subscription options of the forwarding subscriber.The notification can be a recorded announcement, depending onthe exchange parameters. The recorded announcement can alsobe in different languages and/or can be different depending onthe reason for forwarding.

Registration, erasure, activation, and deactivation are performedby the service provider or by the subscriber.

The roaming interrogation is used in the GMSC to interrogatethe HLR for routing information. The called MSISDN number issent to the HLR when requesting routing information. Aforwarded-to number is the result of the interrogation to theHLR. The forwarded-to number is then used to set up the call.The call can be forwarded in the following situations:

• Initiated from GMSC:

- Call forwarding unconditional

- Call forwarding on MS not reachable

• Initiated from MSC/VLR

- Call forwarding on MS busy

- Call forwarding on no reply

- Call forwarding on MS not reachable

The HLR also sends forwarding options to the GMSC. Theforwarding options provide the reason for forwarding the call


– 82 – EN/LZT 123 3972 R2A

and indicates if a notification should be sent to the callingsubscriber.

There are also three Exchange Properties related to CallForwarding services. They are:

Exchange Properties:

CFMAXNUMFORWARD Maximum number of forwardingallowed.

CFNRCVALIDCOND No reachable subscriber condition.Defines if the location is unknown,barred, restricted or purged and arevalid conditions for forwarding thecall according to the service callforwarding on the mobile notreachable.

CFNRTIME Defines the time interval from thepoint when the subscriber is firstalerted until the call is redirected.

Involved blocks: HSSD, HBSGD.

CALL FORWARDING UNCONDITIONAL (CFU)

The unconditional forwarding allows the service provider or theMS, who holds a subscription in the HLR, to forward allincoming calls unconditionally to another directory number.


EN/LZT 123 3972 R2A – 83 –

PSTNHLR

GMSC/VLR

BSCBTS

Signaling path

MS

$�6XEVFU�

%�6XEVFU��

&�6XEVFU��

�

� ��

�

Figure 4-4 Unconditional Call Forwarding

When the HLR checked the MS’s subscription, thesupplementary service CFU was found to be active. The HLRthen returns the C-number to the GMSC instead of an MSRN.

The subscriber can register one Forwarded-to number for eachBasic Service Group with any Basic Service subscribed.

CONDITIONAL CALL FORWARD

Call Forwarding on MS Busy (CFB)

This function forwards the calls for an MS, who holds asubscription in the HLR, to another directory number if thecalled subscriber number is busy.

Call Forwarding on MS Not Reachable (CFNRC)

This function forwards incoming calls to another directorynumber if contact with the MS cannot be established.


– 84 – EN/LZT 123 3972 R2A

Call Forwarding on No Reply (CFNRY)

This function forwards incoming calls to another directorynumber if the called subscriber does not answer a call within apredefined time period.

PSTNHLR

GMSC/VLR

BSCBTS

Signaling pathTraffic path

MS

$�6XEVFU�

%�6XEVFU��

&�6XEVFU��

�

� �

�

�

�

Figure 4-5 Conditional Call Forwarding

The HLR will carry out subscription checks for the MS, then askthe VLR for an MSRN. The MSRN will be returned to theGMSC and then routed to the correct MSC/VLR. When the userdoes not answer the phone, the MSC/VLR will then, with thehelp of function block MRR, route the call to a C-number.

DEFAULT CALL FORWARDING (DCF)

The purpose of this feature is to simplify the call forwardingmechanism to, e.g., the voice mail system. This allows theoperator to register a default forwarded-to number. The purposeis so the caller does not need to set the forwarded-to number tohis/her voice mail. The MSC/VLR views this feature as anormal call forwarding service.


EN/LZT 123 3972 R2A – 85 –

Different subscription options can be created:

• Calling subscriber can receive notification that the call hasbeen forwarded.

• The DCF service can be provided as a default of the callforwarding on busy and/or on no reply and/or on notreachable.

The call forwarding service takes precedence over the DCF andit interacts with other SS’s which is the same as the other callforwarding services. DCF takes precedence over the SinglePersonal Number feature which means that a subscriber shall notbe provided with both Single Personal Number and DCF.

The DCF is provided per Basic Service Group (except SMS)meaning that this feature also can be used with differentforwarded-to numbers, e.g., terminating speech and fax calls.

MONITORING OF CALL FORWARDING REGISTRATION

This feature provides the operator with a mechanism to countthe number of call forwarding, in a certain time interval (givenby command), for a specified subscriber. When the counterreaches specified value (also given by command), an alarm isgenerated to inform the operator that a certain subscriber may bea fraudulent one since he/she is frequently changing the callforwarding number.

After each successful call forwarding initiated by the monitoredsubscriber, the monitoring counter is stepped.

Whenever the counter reaches the defined threshold, an alarm isgenerated and the MSISDN number, date and time of theoccurrence are recorded in a log file.

When an alarm is generated, the counter for this subscriber iscleared and the monitoring continues. The monitoring counter,tied to each monitored subscriber, is cleared for all subscriberswhen the supervision time expires and the monitoring continuesfor the next supervision time interval. The alarm can be reset bycommand and the log file can be printed by command.

This function can be activated per subscriber, per series ofMSISDNs or for all subscribers. It is possible to monitor allforwarded-to number registrations, or only internationalforwarded-to number registrations, with the parameter MCF.


– 86 – EN/LZT 123 3972 R2A

OPERATIONAL INFORMATION:

OPI: “HLR, Monitoring Call Forwarding Registration Activate.”

OPI: “HLR, Monitoring Call Forwarding Registration Deactivate.”

OPI: “HLR, Monitoring Call Forwarding Registration Logging Data,Delete.”

OPI: “HLR, Monitoring Call Forwarding Registration Supervision.”

Exchange properties:

MCFTIMESUP Time period for time supervision

MCFTHRESHOLD Threshold for the number of successfulforwarded-to number registrations

MCFALARM Indication whether the alarm is to begenerated or not

HGMRI, HGMRE, HGMRP for activation, deactivation andprinting of the monitoring of call forwarding registration data.

HGMRI: MSISDNS=34152..., MCF=1/2;

You can specify a single MSISDN or series, and monitorinternational calls or all calls.

HGMSR for alarm reset.

HGMLP, HGMLR for printout and clearing the logging datafile.

Involved blocks: HMCFD, HMCFDA

7-DIGIT DIALING

This feature is intended for CMS 40. It is used if 7 digitfunctionality exists.

Subscribers in the US are familiar with dialing 7 digits to callsubscribers within their own Numbering Plan Area (NPA).Similarly, this feature enables the use of 7 digit dialing fororiginating call set-up and call forwarding SS in the GSMnetwork.

The subscriber does not have to dial their NPA when callingwithin their own NPA from the home PLMN.


EN/LZT 123 3972 R2A – 87 –

The HLR performs the following checks before inserting‘1+NPA’ in front of the number:

• The subscribers own NPA is not 500. If the NPA is 500, theoperation will be rejected with an SS incompatibility error.

• The 7 digit number has the NXX-XXXX format, where N isa digit from 2 to 9 and X is a digit from 0 to 9. If the formatis not NXX-XXXX, the operation will be rejected with anUnexpected Data Value error.

• In the case when the subscriber has the “Dual Numbering”service and the NPAs of the “Main” MSISDN and the“Dual” MSISDN are different, the parameter Basic Serviceis received in the Register SS message. If the parameter isnot received, the operation will be rejected with a DataMissing error.

• In the case when the subscriber has the “Dual Numbering”service and the NPAs of the “Main” MSISDN and the“Dual” MSISDN are different, the parameter Basic Servicedoes not indicate Teleservice “allTeleservices.” If theTeleservices are equal to “allTeleservices,” the operationwill be rejected with SS incompatibility error.

After performing the checks and not finding any errors, the HLRinserts the ‘1+NPA’ in front of the number.

• In the case where the subscriber does not have the “DualNumbering” service, 1+NPA digits are inserted in front ofthe forwarded-to number. This is when the NPA is the NPAof the subscriber who requested the registration.

• In the case where the originating subscriber has the “DualNumbering” and the Teleservice indicates “AuxiliarySpeech”, then the 1+NPA digits of the “Alternate” or “Dual”MSISDN are inserted in front of the forwarded-to number.

• In the case when the originating subscriber has the “DualNumbering” and the Teleservice does not indicates“Auxiliary Speech,” then the 1+NPA digits of the “Main”MSISDN are inserted in front of the forwarded-to number.

• In the case when the subscriber has the “Dual Numbering”and the NPAs of the “Main” MSISDN and the “Dual”MSISDN are the same, then the common NPA will beinserted if the parameter Basic Service is not received in theRegister SS message.

• In the case when the subscriber has the “Dual Numbering”and the NPAs of the “Main” MSISDN and the “Dual”MSISDN are the same, then the common NPA will be


– 88 – EN/LZT 123 3972 R2A

inserted if the parameter Basic Service received in theRegister SS message indicates the Teleservice is equal to“allTeleservices.”

7 Digit Forwarded-to Number Registration

This allows the mobile subscriber in the GSM network toregister a 7 digit forwarded-to number in the HLR. An MS mayalways register a 7-digit forwarded-to number using Register SSMAP V.1 or V.2. When this is received, the HLR will check ifthe address is unknown and if the digit structure is NXX-XXXXwhere N=2-9, X=0-9. If the structure is not correct, then theerror “Unexpected Data Value” is returned.

Before checking that the number received is not the subscriber’sown MSISDN or an additional number associated with thesubscriber, the following checks are performed:

1. If Basic Service Group (BSG) parameter is not received, thefollowing checks are completed:

– If the subscriber does not have “Dual Number” service, itis checked that the NPA of subscriber’s Main MSISDN isnot 500. If it is 500, the error “SS Incompatibility” isreturned.

– If the subscriber has “Dual Number” service and theNPAs of the “Main” MSISDN and the “Dual” MSISDNare equal, it is checked that it is not 500. If it is 500, theerror “SS Incompatibility” is returned.

– If the subscriber has “Dual Number” service and theNPAs of the “Main” MSISDN and the “Dual” MSISDNare different, the error “Data Missing” is returned.

2. If BSG parameter is received and it indicates thatTeleservice is equal to “allTeleservices” or to“allTeleservices except Short message,” the followingchecks are completed:

– If the subscriber does not have “Dual Number” service, itis checked that the NPA of the subscriber’s MainMSISDN is not 500. If it is 500, the error “SSIncompatibility” is returned.

– If the subscriber has “Dual Number” service and NPAs ofthe “Main” MSISDN and the “Dual” MSISDN are equal,it is checked that it is not 500. If it is 500, the error “SSIncompatibility” is returned.

– If the subscriber has “Dual Number” service and NPAs ofthe “Main” MSISDN and the “Dual” MSISDN are


EN/LZT 123 3972 R2A – 89 –

different, the error “SS Incompatibility” is returned.

3. If BSG parameter is received and it indicates thatTeleservice is equal to “Auxiliary Telephony” or to“Auxiliary Speech”, it is checked that the NPA of the “Dual”MSISDN is not 500.

4. If BSG parameter is received and it is different to“allTeleservices.” AllTeleservices, except Short Message“Auxiliary Telephony” or “Auxiliary Speech”, it is checkedthat the NPA of the “Main” MSISDN is not 500. If it is 500,the error “SS Incompatibility” is returned.

If all the checks performed in the previous chapters are passedand no errors were found, HLR inserts 1+NPA in front of theforwarded-to number. The inserted NPA digits are:

• The same as the subscriber’s “Main” MSISDN if he/shedoes not have “Dual Number” service.

• If the subscriber has “Dual Number” service and the NPAsof the “Main” MSISDN and the “Dual” MSISDN are equal,the common NPA will be inserted.

If the subscriber has “Dual Number” service and the NPAs ofthe “Main” MSISDN and the “Dual” MSISDN are different, theNPA digits of the “Dual” MSISDN will be inserted if theparameter Basic Service indicates that Teleservice is equal to“Auxiliary Telephony” or to “Auxiliary Speech”. Otherwise, theNPA digits of the “Main” MSISDN will be inserted.


– 90 – EN/LZT 123 3972 R2A

CALL BARRING SERVICES

The purpose of this feature is to bar calls. Calls can be barred inthe following situations:

• Call Barring of All Incoming Calls (BAIC)

• Call Barring of All Outgoing Calls (BAOC)

• Call Barring of Outgoing International Calls (BOIC)

• Call Barring of Outgoing International calls EXcept thosedirected to the Home PLMN country (BOIEXH)

• Call Barring of Incoming Calls when Roaming Outside thehome PLMN country (BICRO)

Call barring services enables the mobile subscriber to preventthe use of their subscription for specified types of calls.However, set-up emergency calls remains unaffected.

The HLR performs call barring services when indicated by thesubscription (parameter SUD). This means that the relevantbarring data constitutes part of the mobile subscribers data in theHLR.

The subscriber can select two subscription options regarding thecontrol of barring services. Either the service is controlled by theservices provider only, or by the service provider and the mobilesubscriber using a password.

Involved blocks: HSSD.

OPERATOR DETERMINED BARRING

The Operator Determined Barring refers to the administrativemeans used by the operator in order to bar the Mobile Stations(MS) from outgoing and/or incoming calls for administrativereasons.

• A short message is handled as a call

• This feature lets the operator bar the MS to access any GSMservices when roaming into a certain area

• Only the operator may activate and deactivate the features

The following Operator Determined Barrings are available inHLR:


EN/LZT 123 3972 R2A – 91 –

• Barring of All incoming and outgoing calls (OBA)

• Barring of all Incoming calls (OBI)

• Barring of all Outgoing calls (OBO)

• Barring of Outgoing Premium Rate calls, Entertainment(OBOPRE)

• Barring of Outgoing Premium Rate calls, Information(OBOPRI)

• Barring of Registration of Forwarded-to number (OBRF)

• Barring of Supplementary Services Management (OBSSM)

• Barring of Incoming Inter-Zonal calls (OBZI)

• Barring of Outcoming Inter-Zonal calls (OBZO)

• When registered in the HPLMN Operator Specific Barring,type 1 (OSB1)




• Barring of Roaming (OBR)

The subscriber record in HLR contains information which pointsout which barring programs are active for the subscriber. Thisinformation may be set by the operator. The subscriber data isinserted into MSC/VLR by HLR. MSC/VLR will bar outgoingcalls according to access barring analysis: E.g., internationalcalls except those directed to the HPLMN country. If anincoming call arrives for the subscriber and the subscriber hasincoming calls barred, the HLR will not forward routinginformation to MSC/VLR. The answer to the roaming routinginterrogation will indicate that the call was barred.

If the call is a mobile originated short message, the servicecenter number is analyzed so it is able to point out thedestination instead of the called subscriber number.

An extended analysis should be defined if the feature, which isoptional and controlled by exchange property , will be used.

There are some Exchange Properties in the ApplicatonInformation of block HRS and its relation.


– 92 – EN/LZT 123 3972 R2A

OPERATOR DETERMINED BARRING IN HLR FOR INTER-ZONALCALLS

Operator Determined Barring of inter-zonal calls gives theoperator the ability to restrict calls within a world zone (e.g.world zone one with USA, Canada, Puerto Rico, Jamaica, etc.).

Only the operator may activate and deactivate the feature.

The following barring options are available with this feature:

• Barring of incoming calls when roaming outside the zone ofthe HPLMN country

• Barring of outgoing inter-zonal calls

• Barring of outgoing inter-zonal calls except those directed tothe HPLMN country

• Barring of outgoing international calls except those directedto the HPLMN country AND barring of outgoing inter-zonalcalls

Only one of the barring services, from the last three options, canbe activated at the same time.

The subscriber record in HLR contains information which pointsout which barring options are active for the subscriber. Thisinformation may be set by the operator.

An extended analysis should be defined if the feature, which iscontrolled by the optionally parameter in APZ, is to be used.

A “zone” is defined by the digit allocated as the country code oras the first digit of the country code. Valid values are from 1 to9. Zones 3 and 4 are treated as one.

OPERATOR DETERMINED BARRING IN HLR FOR CALLFORWARDED-TO NUMBERS

Operator Determined Barring for call forwarded-to numbersprovides the operator with a new set of barring options tocontrol subscribers use of the call forwarding feature.

The following Operator Determined Barring options areavailable with this feature:

• Barring of registration of any call forwarded-to number

• Barring of any international call forwarded-to number


EN/LZT 123 3972 R2A – 93 –

• Barring of registration of any international call forwarded-tonumber except to a number within the HPLMN country

• Barring of registration of inter-zonal call forwarded-tonumber

• Barring of registration of inter-zonal call forwarded-tonumber except to a number within the HPLMN country

Only one of these barring options can be activated at the sametime and only the operator may activate and deactivate them.

The subscriber record in HLR contains information which pointsout which barring options are active for the subscriber. Thisinformation may be set by the operator.

An extended analysis should be defined if the feature, which isoptional and controlled by the APZ optionally parameter, isgoing to be used.

Involved blocks: HSDH, HSDH2, HDSH3.


– 94 – EN/LZT 123 3972 R2A

ERICSSON PROPRIETARY SERVICES

Ericsson Proprietary Supplementary Services are PLMN specificSupplementary Services (SS), defined by Ericsson, but notincluded in the GSM specification. A PLMN specific SS is aservice that only has meaning in a PLMN.

In the HLR it is possible to define (by commands) the PLMNspecific Supplementary Service (PSS) codes and PRIvate Tag(PRIT) values that are valid for a specific MSC/VLR area.

The administration of these features will be carried out by theexisting commands for change and a printout of the subscriberdata and profile administration. Then, these features will notrequire any of their own commands.

The Ericsson Proprietary Services that can be assigned to asubscriber are:

• Single Personal Number (SPN)

• Immediate Call Itemization (ICI)

• Originating Intelligent Network (OIN)

• Terminating Intelligent Network (TIN)

• Dual Number (DN)

• Originating IN Category Key (OICK)

• Terminating IN Category Key (TICK)

• Channel Allocation Priority Level (CAPL)

• Subscription TYPE (STYPE/ST)

• ACcount Codes (ACC)

This information will be stored in block HSD as a newPermanent Subscriber Data.


EN/LZT 123 3972 R2A – 95 –

SHORT MESSAGE SERVICES

When a subscriber subscribes to a mobile terminated or mobileoriginated Short Message Service (SMS) then the subscriberwill be able to receive short messages.

When a Short Message is being received by a mobile subscriber,the HLR checks if the service is provisioned, if any barring isactive, and if the subscriber is absent.

In case of an unsuccessful delivery of a short message, theService “Messages-Waiting” provides the HLR with theinformation that there is a message in the Short MessageService-Center (SMS-C) waiting. The information is located inthe HLR Messages-Waiting-Data (MWD), which contains a listof SMS-C addresses that have made unsuccessful deliveryattempts. The HLR informs the SMS-C when the mobile isavailable.

MOBILE TERMINATED SHORT MESSAGE SERVICE SUBSCRIPTION

This function provides the administrative means to allow an MSto receive short messages.

SHORT MESSAGE ROAMING ROUTING

This function provides SMS-GMSC routing information toforward mobile terminated short messages.

When the HLR receives the interrogation to locate thesubscriber from the GMSC, instead of sending a roamingnumber back to the GMSC (no speech channel is needed), theHLR sends back the VLR address to the GMSC.


– 96 – EN/LZT 123 3972 R2A

Forward mobile terminated Short MessageSend routing information for Short MessageForward informationForward Short MessageResult MessageResult Message

1.2.3.4.5.6.

(1)

(6)(4)

(3)

(5)

(2)

Figure 4-6 Mobile Terminating SMS

SET MESSAGE WAITING DATA

If the transmission of a Short Message (SM) is not successful,the VLR sends a “not successful” message back to the HLR. Aflag is set in the HLR and it requests the inclusion of the ServiceCenter address, in the Message Waiting Data. The ServiceCenter is also informed and the SM is stored.

Figure 4-7 Unsuccessful Message Transfer

As soon as the Mobile Subscriber is available again, the HLRwill be informed.

NOTE MS PRESENT

This function informs the HLR when the MS is reachable again.The HLR has stored the SC-address (message waiting list) andsends the “alert” to the Inter-Working MSC (IWMSC).


EN/LZT 123 3972 R2A – 97 –

SHORT MESSAGE ALERT

The corresponding Service Center is alerted when the MS is ableto receive Short Messages, after performing an unsuccessfulshort message transfer.

AlertServiceCenter

Figure 4-8 Note MS Present (Ready for SM in MAP V2)

HIGH PENETRATION NOTIFICATION

High Penetration Notification will allow the subscriber toreceive a notification when a Mobile Terminated Short Messagehas failed due to no paging response.

The feature makes the subscriber reachable everywhere, whichmight be a big issue when choosing a satellite telephony service.By using this service, the satellite operator drastically increasesits coverage to all indoor area environments which the signalnormally reach. This service will deliver very short messagesutilizing the high power capacity in the satellites.

Subscription to the High Penetration Notification service ishandled by the HLR and the SUD=HPN. Then the HighPenetration Notification subscriber data is provided to theMSC/VLR.

MAP V3 is required for this feature.

HLR SHORT MESSAGE SERVICE CENTER

There is no command needed in the HLR to specify ServiceCenter addresses because they are inserted automatically, whenthe subscriber is not reachable. However, there is an OPI forassociated printouts.


– 98 – EN/LZT 123 3972 R2A

OPERATIONAL INFORMATION

OPI: “HLR Service Center Address Data Printouts”

HGSCP;

Prints out all stored Service Center addresses and the number ofassociated subscribers.

HGMWP:MSISDN=3415100001;

Prints the Service Center addresses when messages for thesubscriber are waiting within the given MSISDN.


EN/LZT 123 3972 R2A – 99 –

FLEXIBLE NUMBERING

The purpose of the Flexible NumbeRing (FNR) feature is toenable mobile operators to allocate subscriber identities in aflexible way. This is to avoid today’s restrictions on thesubscribers ability to choose an MSISDN which is restricted tothe MSISDN number series assigned to the HLR. This is wherethe corresponding IMSI number series is held once thesubscriber obtains the SIM card.

In the GSM mobile systems, a node may have the need tocommunicate with the HLR regarding a mobile stationsubscriber of which the HLR address is unknown. The node useseither the IMSI or the MSISDN to address the HLR, dependingupon the traffic case and on which identity is available.

When a mobile terminating call enters the GSM network, theGMSC needs to interrogate the HLR in order to find out wherethe mobile station is located. The called subscriber MSISDN, isused in the SCCP analysis to route the interrogation message tothe HLR where the subscription is held. To make the SCCPanalysis reasonable, MSISDN numbers belonging to certainHLRs are grouped together. In other words, consecutive IMSIand MSISDN numbers (in a series) cannot belong to differentHLRs.

This is not a problem in a single HLR environment. However, ina multiple HLR environment it is necessary that the SubscriberIdentity Module (SIM) cards (containing the IMSI) must be pre-packaged in groups together with the MSISDN number seriesused in that particular HLR.

The purpose of this feature is to add flexibility in the system tomake it possible for the service provider to allocate anyMSISDN number to an IMSI.

If this function is introduced in an existing network, the SCCPanalysis in the concerned nodes (GMSCs and STPs) must bemodified to route the interrogation message “RoutingInformation Request” to the FNR instead of routing it directly tothe HLR.

It must be assured that the messages arrive at the FNR with theMSISDN in the Global Title field of the “Called Party Address”parameter.


– 100 – EN/LZT 123 3972 R2A

Technical Solution

The technical solution implies the creation of an application thatcan be seen as an extension to SCCP. The GMSC sends theinterrogation message to the FNR. The message is routed on thecalled subscribers MSISDN, using the SCCP analysis. The FNRsearches for the MSISDN number in the FNR data base, whichcontains the connection between the subscribers MSISDN, IMSIand MGT. If the MSISDN is found, the corresponding MGT iscollected, so the interrogation message can be routed to thecorrect HLR. It may be routed to the HLR node where the realsubscription (IMSI plus the rest of subscriber data) is kept.

GMSC FNR HLRE.164

MSISDN

E.214

MGT

Figure 4-9 FNR function

The FNR functionality can be implemented in the mobilenetwork with different physical locations and configurations.This is due to the Application Modularity concept, which wasestablished in APT 210 15.

One possible configuration is the FNR integrated with a HLR ora GMSC as shown in figure 4-6.

# 7 network

SCCPSCCP

GMSC FNR HLR

Figure 4-10 FNR/HLR

Another possible configuration is the FNR is implemented as astand-alone.

In order to route the interrogation message to the correct HLR,the FNR needs a data base containing the connection betweenthe MSISDN, IMSI and MGT. This connection is defined by thecommand HGFNI:

HGFNI: MSISDN= 3415100001, IMSI= 24450100001;


EN/LZT 123 3972 R2A – 101 –

The MGT is obtained at connection of the MSISDN-IMSI whichis done by accessing a translation table in block FLNAN,containing the translation data.

When the HGFNI command is entered, the leading digits of theIMSI number are analyzed. If they are found in the translationtable, the IMSI is modified to a MGT and the three differentnumber types, MSISDN, IMSI and MGT, are stored in the FNRdata base.

240 01 1

IMSI MGT

240 01 3

240 01 2

46 707 5

46 707 6

46 707 7

240 01 1000000002 46 707 5000000002

HLR 1

HLR 2

HLR 3

Figure 4-11 FNR Translation Table

This relation must be defined for all MSISDN numbers that arerouted through the FNR. If a MSISDN is not found (not defined)in the data base, then the message will be routed to a defaultHLR using a default IMSI which is defined by the commandHGFNC:

HGFNC: IMSI= 2445010;

There is also a possibility for fast reading of the MSISDN-IMSIpairs from an external file and definition of them in the FlexibleNumbering data base. For this purpose the file FLNUMFILE isused. It is a copy of the file HPSDFOAFILE obtained from theFile Output for subscriber data in the HLR and must be defined.


– 102 – EN/LZT 123 3972 R2A

HLR

FNR

HGPFI:IMSIS=ALL;

HPSDFOAFILE

HLR commands

FLNUMFILE

HGFII;

FNR commands

COPY: INFITINFET(INFII)(AI:HPSDFOA)

AXE I/O commands

1.

2.

3.

Figure 4-12 Loading the FNR with information about MSISDN-IMSI pairs already existing in the HLR

Call to a Mobile Subscriber (MS) is the only traffic case affectedby the introduction of FNR node in a mobile network.

When adding the Flexible Numbering functionality in thenetwork, the interrogation messages are no longer to be routedtowards a specific HLR. Instead, they are routed via the FNR.This will bring some changes in the SCCP data in the GMSCand HLR nodes.

HLR1 HLR2 HLR3

GMSC

Figure 4-13 Network without FNR

All MSISDN numbers analyzed in the GMSC will get a GlobalTitle Routing Case (GTRC) pointing towards the FNR. Thedestination SubSystem Number (SSN) included in the message,


EN/LZT 123 3972 R2A – 103 –

must be changed to address the FNR (default SSN=253) insteadthe default value of HLR (SSN=6).

HLR1 HLR2 HLR3

GMSC

FNR

1

2

3

Figure 4-14 Network with FNR


– 104 – EN/LZT 123 3972 R2A

DATA CALLS IN HLR

BEARER CAPABILITIES

Within Integrated Services Digital Network (ISDN), PublicSwitched Telephone Network (PSTN) and Global System forMobile communication (GSM), a number of different servicesare available. These services include speech, facsimile, and datatransmission with different user rates.

The receiving node, as well as intermediate nodes, needinformation on what service is requested and how the service isto be performed, e.g., what user rate is used.

Bearer capabilities (BC) contain this information. BCs are partof the User Service Information Element in the CALL OUTIAM message, and the Bearer Capability Information Element(BCIE) in the SETUP message.

1RWH� This only applies to ISDN and GSM since PSTN FDQQRWprovide this type of information.

Different coding schemes are used in ISDN and GSM becausedifferent transmission requirements must be met. They arereferred to as ISDN BC and GSM BC.

For every call set up from ISDN or GSM, the BC informationdescribes the type of service requested. However, this is notpossible in a situation when a call is received from the PSTN, soadditional MSISDN numbers are used instead.

BEARER CAPABILITY ADMINISTRATION

During Roaming Routing Determination, a bearer capabilityanalysis is performed in function block HBCAN (Home BearerCapability Analysis). A different coding scheme for the BC isused and is needed as in GSM and in the ISDN. The reason isthat in ISDN a wider range of services can be provided.

The analysis is performed in several steps:

1. Translation from ISDN-BC into GSM-BC.

2. Translation from GSM-BC into the GSM defined BasicService Group (BSG) will be used for checking whichsupplementary services are applicable for the wanted BSG.


EN/LZT 123 3972 R2A – 105 –

3. Finally, an internally BC number is derived for checking ifthe service is supported by the HLR.

In the following the applicable supplementary services will be checkedif they are subscribed, and if so, if they are activated.

All GSM BCs supported by the HLR must be defined bycommand in the HLR.


OPI:HLR Mobile Subscriber GSM Bearer Capability Define

OPI:HLR Mobile Subscriber GSM Bearer Capability Delete

HGBDI:BC=15, FAX, RC=5-0-3, ACC=0-3-0, ITN=0;

Bearer capability number 15, representing the TeleserviceFacsimile Group 3, is assigned to the following values:

• RC (Radio Channel) consists of parameters UR-MT-IR

UR (User rate) is 9.6 Kbit/s

MT (Modem Type) is none

IR (Intermediate Rate) is 16 Kbit/s

• ACC (Information Access) consists of RA-S-SA

RA (Rate Adaptation) is no rate adaptation

S (Structure) is unstructured

SA (Synchronous/Asynchronous) is synchronous

Interworking with Terminating Network (ITN) may consist oftwo parameters, Connection Element (CE) in this case indicatestransparent.

New parameter and units for this command must be includedwhen defining the High Speed Circuit Switched Data Servicewhich will be explained later in this chapter.

HGBDI:BC=19, ALTFAX, RC=5-0-3, ACC=030, ITN=0;

Bearer capability 19 is coded for alternate speech/facsimilegroup 3. Starting with speech: user rate to 9.6 Kbit/s, modemtype to none, intermediate rate to 16 Kbit/s, no rate adaptation,structure to unstructured, synchronous, connection element totransparent, representing the teleservice alternate speech andfacsimile group 3.


– 106 – EN/LZT 123 3972 R2A

The BC numbers can be freely assigned by the operator exceptfor four reserved values:

• BC=0 represents teleservice “Telephony”

• BC=1 represents teleservice “Auxiliary Speech”

• BC=8 represents the basic service “Altern. Speech andAutom. Facsimile Group 3”

• BC=9 represents the basic service ” “Autom. Facsimile Group 3”

HGBDE:BC=15;

Bearer capability 15 is not defined further.

MULTIPLE NUMBERING SCHEME

The Multiple Numbering Scheme allows the Home Public LandMobile Network (HPLMN) to allocate several MSISDNs to onesubscriber. Each MSISDN is associated with one BC.

When a call comes from the PSTN, the HLR determines whichBC is required, by using an additional MSISDN assigned to thesubscriber.

A subscriber must have an additional MSISDN number for eachtype of service, and the correct MSISDN must be dialed for eachtype of call. One subscriber can have a maximum of 16 differentadditional numbers (ADDMAXNUM).

E.g.: A subscriber would need one number for telephonyservice, a second for asynchronous data service 2400 kbit/sec,and a third for automatic fax group 3.

The additional numbers are tied to a specific service in the HLR.This service is described by means of a GSM BC.

Figure 4-15 is an overview of how the service is retrieved froman incoming MSISDN in HLR. The missing BC is generated inthe HLR.


EN/LZT 123 3972 R2A – 107 –

ADD

not relevant

HBCAN

BC serviceBCIE

MSISDN

HSNANMain

AdditionalHASND

ADD. No. BC BC

SER.

Figure 4-15 MSISDN Analysis

Calls Using Additional MSISDN

Terminating calls using additional MSISDNs without ISDN-BCcodes are handled according to the BS code obtained from theGSM-BC linked to that number. This linked BC code is thensent to the VLR.

SINGLE NUMBERING SCHEME

The single numbering scheme is introduced with Ericsson’sGSM System.

This scheme allows the HPLMN to allocate one MSISDN to asubscriber, which is applicable to all services.

In this scheme, the subscriber’s main MSISDN is also defined asan additional MSISDN. This provides the ability to link a BC tothe main MSISDN and allows terminating calls to act as callsusing an additional MSISDN.

Calls Using Main MSISDN and no ISDN-BC Available

When the main MSISDN is used, but no ISDN-BC is available,the “Default Basic Service Group” linked to the subscriberhandles the call. A GSM-BC is not sent to the VLR because aspecific BC cannot be associated to the main MSISDN. In thiscase, the mobile station will return a complete GSM-BC in theCall Confirmed message indicating the service required by themobile subscriber.

Some mobile stations do not return the GSM-BC in the CallConfirmed message to the VLR. It is necessary to have anadditional MSISDN to ensure that the VLR receives a BC from


– 108 – EN/LZT 123 3972 R2A

the HLR for subscribers with only one BS different fromtelephony.

This modification allows the main MSISDN to be defined as itsown additional MSISDN. Calls received without a BC can behandled using additional MSISDN.

Command HGAMI

Command HGAMI initiates the subscription of MSISDN as anadditional MSISDN linked to a specific GSM-BC for asubscriber. Both MSISDN and AMSISDN will have the abilityto contain the same number.


OPI: HLR Mobile Subscriber Additional MSISDN Initiate

OPI: HLR Mobile Subscriber Additional MSISDN End

HGAMI: MSISDN=3415100001, AMSISDN=3415100010,BC=15;

The number 3415100010 is the additional number for the BCnumber 15 and for the subscription whose main MSISDN is3415100001.

HGAME:AMSISDN=3415100010;

The number 3415100010 is not an additional number anymore.

Involved blocks: HASND.


EN/LZT 123 3972 R2A – 109 –

ISDN ORIGINATING DATA CALL

HLR

ISDN

DTI

GMSC/ VLR

BSC

PAGINGISDN BC + B - NUMBER

1

2

3

4

5

6

78

9

Figure 4-16 ISDN Originating Data Call to PLMN

When an incoming Data call from ISDN is received in theGMSC, the ISDN Bearer Capability (ISDN BC) is sent in theSET UP message (step1).

The GMSC sends a request for routing information to the HLR,to locate the subscriber. Included in this message is the ISDNBC (step 2).

The HLR translates the received ISDN-BC into a GSM-BC(hardcoded in block HBCAN).

For instance, the call from ISDN was an asynchronous 9600baud/s data circuit call. That call corresponds to Bearer Service26 according to the GSM specification.

A check is now made to see if the called subscriber has asubscription for this bearer service. If they have, it is defined asfollows (step 3):

HGSDC:MSISDN=34 151..., SUD=BS26;

The BC, from the list of supported BCs, is defined with thecommand HGBDI and is retrieved. If the dialed B-number wasan additional MSISDN(AMSISDN), which could be the case


– 110 – EN/LZT 123 3972 R2A

even though the call was initiated from ISDN, the HLR checkswhich BC it is connected to.

HGAMI:MSISDN=34 151.., AMSISDN=34250...,BC=269;

In HGBDI, the characteristics of the BC=269 are collected.

HGBDI: BC=269, UDI, RC=5-0-3, ACC=1-0-1, ITN=1-12,ACCST=1-0-1-3;

If the MSISDN has the subscription, the HLR sends a messageto the VLR, where the subscriber currently is located, asking fora roaming number (step 4). In the message, the translated GSMBC is also included, retrieved either from translation of theISDN BC or the BC defined in HGAMI.

The VLR temporarily connects a roaming number to the dialedsubscriber and sends it back to the HLR (step 5). The HLRsends the roaming number back to the GMSC (step 6).

This number is analyzed in the VLR and the Telecommunicationservice analysis is invoked. Since it is a data call, the outputfrom the analysis leads to a route going towards the DTI ( or tothe GIWU) (step7).

When the DTI (or GIWU) has connected the proper equipment,(step 8) the MS is then paged (step 9). Upon reception of thepage response from the MS, the call is established and the datafile can be sent.

HIGH SPEED CIRCUIT SWITCHED DATA (HSCSD) IN HLR

This service enables the mobile station subscriber to establish adata or fax connection with speeds above 9.6 kbps. To achievehigher speeds two or more time slots in one radio channel isused. Each time slot being capable of carrying 9.6 kbps.

HSCSD will be implemented in GSM 1900 standard in the sameway it is done for GSM 900 and 1800. However, it is notincluded in any GSM 1900 specifications. This functionalityaffects the following services:

• Asynchronous services:

– New user rates: 14.4, 19.2, 28.8 and 38.4 kbit/s.

– New modem types: V.32bis and V.34.

• Synchronous services:


EN/LZT 123 3972 R2A – 111 –

– New user rates: 14.4, 19.2, 28.8, 38.4, 48 and 56 kbit/s.


– RDI is also supported.

• High Speed Fax and alternate Speech/Fax

– New user rate: 14.4 kbit/s.


The inclusion of HSCSD services implies handling of two newBearer Services in the HLR. These Bearer Services are GeneralAsynchronous Bearer Service (BS2G) for Asynchronoustransmissions, and General Synchronous Bearer Service(BS3G) for synchronous. The subscription of one of theseBearer Services is incompatible with subscription of the otherBearer Service which is included in the same BSG.

For handling HSCSD terminating calls properly, a new interfacetowards the data base for optimizing the analysis of bearercapabilities will be defined.

BS

3671

BTS

BSC

DTI

V.34 Modem

V.34 Modem

MSC

02'(0�6(59,&(02'(0�6(59,&(

Transparent: up to 3 timeslotsNon Transparent: up to 4 timeslots

Transparent: up to 28.8 kbpsNon Transparent: up to 33.6 kbps

Figure 4-17 HSCSD módem service


– 112 – EN/LZT 123 3972 R2A

BS

,6'1

BTS

BSC

DTI

V.110 rateadaptation

V.110 TA

MSC

8',�6(59,&(8',�6(59,&(

Transparent: up to 4 timeslotsNon Transparent: up to 4 timeslots

Transparent: up to 38.4 kbpsNon Transparent: up to 38.4 kbps-

Figure 4-18 HSCSD over ISDN

Definitions

High Speed Circuit Switched Data service (HSCSD):

HSCSD services are GSM phase 2+ services which requires amulti-slot configuration. This configuration is useful for higherrates of data transmission and allowing new services, such asVideo communications, in the GSM network.

General Bearer Services:

A single service is defined independent of the fixed networkused rate. A subscription to a General Bearer Servicecomprises the subscription to all individual single services ofits group. A subscriber shall not have a simultaneoussubscription to a General Bearer Service, and any of theindividual single services covered by the General BearerService.

Fall-Back Bearer Service:

The Bearer Service is used when the General Bearer Service isincluded in the same BSG and the BS is not supported for anyother reason. E.g., communication with a MSC/VLR that doesnot support subscription to General Bearer Services.


EN/LZT 123 3972 R2A – 113 –

The provision of this service is optional and it is done on asubscriber basis. It is only used if there is no other dataavailable.

Implementation

The introduction of HSCSD implies the creation of 2 newSUDs/BSs in the HLR. These SUDs are:

BS2G Asynchronous General Bearer Service, which isincluded in the BSG BS 20. The string assigned forthis SUD is ‘BS2G.’ It is referred to in the GSMdocuments as BS20.

BS3G Synchronous General Bearer Service, which isincluded in the BSG BS30. The string assigned forthis SUD is ‘BS3G.’ It is referred to in the GSMdocuments as BS30.

Apart from these SUDs, two more SUDs must be defined in the HLR tosupport the subscription of the Fall-Back Bearer Service associated withthe corresponding General Bearer Service subscribed. These 2 newSUDs are:

BS2F Fall-Back Bearer Service is used when the BS2G,general Asynchronous Bearer Service, is notsupported by MSC/VLR.

The possible values of this SUD are:

0 No Fall-back BS subscribed1 The Fall-back BS is BS212 The Fall-back BS is BS223 The Fall-back BS is BS244 The Fall-back BS is BS255 The Fall-back BS is BS26

BS3F Fall-Back Bearer Service is used when the BS3G,general Asynchronous Bearer Service, is notsupported by MSC/VLR.

The possible values of this SUD are:

0 No Fall-back BS subscribed1 The Fall-back BS is BS312 The Fall-back BS is BS323 The Fall-back BS is BS33


– 114 – EN/LZT 123 3972 R2A

4 The Fall-back BS is BS34

The 4 SUDs, BS2G, BS2F, BS3G and BS3F, must be includedin the process of execution of this command. All parametersrelated to each one of these SUDs must be included in blockHTRAN, and space must be reserved in the subscriber datarecords (block HSD) to store the subscription of these newservices.

Format of the HGSDC command is not changed, but COD mustinclude fault codes to indicate incompatibility among services.

HGBDI Command:

New parameters and units for defining the HSCSD BearerCapability and the new fixed network interface, must beincluded. Command format remains the same:

Restricted Digital Information (RDI).

If it is present, the presence of parameter Information ACCessSTructure (ACCST) is mandatory.

The new units (omt and fnur) are included as part of thegeneral parameter Radio Channel (RC) as follows:

omt Other Modem Type

0 No other modem type1 V.32 bis2 V.34

fnur Fixed Network User Rate

0 Not applicable1 9,6 kbit/s2 14,4 kbit/s3 19,2 kbit/s4 28,8 kbit/s5 38,4 kbit/s6 48,0 kbit/s7 56,0 kbit/s8 64,0 kbit/s

Business

Hlr04r2a