Test procedure

A PDP context activation is requested by the SS with the transaction identifier set to ’1’. The UE shall not
respond to this request.
A PDP context is then activated from the UE and accepted from SS. A deactivate message is then sent from the
SS with a different transaction identifier to the one used in the activate request message sent by the UE. The UE
shall reply with a SM STATUS message with cause #81 ’invalid transaction identifier value’ and transaction
identifier same as one used in deactivate message.
A modify message is then sent from the SS with a different transaction identifier to the one used in the activate
request message sent by the UE. The UE shall reply with a SM STATUS message with cause #81 ’invalid
transaction identifier value’ and transaction identifier same as one used in modify message.
A modify request message is then sent from the SS with transaction identifier equal to the one used in the
activate request message sent by the UE. The UE shall reply with a modify accept message.

Two invalid accept messages are then sent by the SS with T3380 seconds between them. After a further T3380
seconds a valid accept message is sent by the SS.
A deactivate message is then sent from the SS with the transaction identifier set to ’111’. The UE shall reply
with a SM STATUS message with transaction identifier set to ’111’.
A deactivate message is then sent from the SS with a different transaction identifier to the one used in the
activate request message sent by the UE. The UE shall reply with a SM STATUS message with cause #81
’invalid transaction identifier value’.
Three invalid modification messages are then sent to the UE in turn. The UE shall respond each time with a SM-
STATUS message with cause # 96 ”invalid mandatory information”.

The Home Location Register is a database within the Home Public Land Mobile Network.
1. It provides routing information for Mobile Terminated calls and Short Message Service. It is also
responsible for the maintenance of user subscription information.
2. This is distributed to the relevant VLR -Visitor Location Register or SGSN - Serving GPRS
Support Node through the attach process and mobility management procedures such as Location
Area and Routing Area updates.
3. HLR stores and manages all mobile subscriptions belonging to a specific operator. The HLR
is considered the most important database because it stores permanent data about subscribers,
including subscriber’s supplementary services, location information, and. authentication
parameters buys When a person a subscription, it is registered in the operator’s HLR.
4. The HLR can be implemented with the MSC/VLR or as a stand-alone database.
5. A HLR contains user information such as account information, account status, user
preferences, features subscribed to by the user, user’s current location, etc. The data stored in
HLRs for the different types of networks is similar but does differ in some details.
6. HLRs are used by the Mobile Switching Centers (MSCs) to originate and deliver arriving mobile
calls.
HLR Redundancy
When a single HLR fails, all subscribers with records in that HLR will not be able to roam or receive
calls. HLR Redundancy can prevent such a loss of subscriber activity. This feature is achieved by
having an additional HLR node for each HLR node in the network. HLR Redundancy provides
protection against disaster situations such as fire at an HLR site. At the same time, it will give
protection against Signalling failures towards an HLR and will also lower the lack of availability
caused by HLR restarts.
With this feature, the subscriber can make and receive calls even in disastrous situations like an
earthquake with little or no change in network continuity or functionality. The HLR Redundancy
feature, allows failure to be invisible to the network and the subscriber. A mated HLR is introduced
in such a way that subscribers and load are shared in normal operation, and when one HLR fails,
the other picks up all traffic normally routed to the pair.
2. VLR
A VLR is a database, similar to a HLR, which is used by the mobile network to temporarily hold
profiles of roaming users (users outside their home area). This VLR data is based on the user
information retrieved from a HLR. MSCs use a VLR to handle roaming users.
Database contains information about all mobile stations currently located in the MSC service area.
VLR contains temporary subscriber information needed by the MSC to provide service for visiting