Rejected Location Update Requests (Interface Unavailable)

Dear Huawei experts,

What does this location update counter mean?
LA307:Number of Rejected Location Update Requests (Interface Unavailable)(none)

Basically what Interface does it refer?

BR//
Gogo

any help PLZ? Still waiting for your answers ...

Of all the different varieties of software programs that you can buy unlock iphone 4 Newport Seashore, Outings On the ocean will assist you to see
Discover More Here confidently by just grasping basic unlock iphone 4
unlock iPhone 4
protectively via studying methods http://unlockiphone4dd.info .

Where did you get this message? in MSC or BSC?

in the BSC, in huawei cells have this problems when i have sites without swapped and different lac

Quote:

---

Dear Huawei experts,

What does this location update counter mean?
LA307:Number of Rejected Location Update Requests (Interface Unavailable)(none)

Basically what Interface does it refer?

---

look here your failures are among those followingso you must make a trace of the cell and then fix the issue :-)


Location Update Not Started or Terminated on the MS Side

This describes the fault, probable causes, and handling suggestions.
Description
The location update procedure is not started or is terminated.
Analysis
The probable causes are as follows:
l Access barred because of access class control
The location update procedure is not started. The MS stays in the current serving cell and
starts the normal cell reselection procedure. The MS starts the location update procedure
as soon as it gains access or at cell change.
l Receiving an Immediate Assignment Reject message during random access (in A/Gb mode
only)
The location update procedure is not started. The MS stays in the selected serving cell and
starts the normal cell selection procedure. Timer T3122 is reset when a cell change occurs.
The location update procedure is started as soon as timer T3122 expires.
l Random access failure (in A/Gb mode only)
Timer T3213 is started when random access fails. When it expires, the procedure is
attempted again if still necessary. If two successive random access attempts fail, the location
update procedure attempt is terminated.
l RR connection failure
The location update procedure is terminated.
l T3212 expiry
The location update and the RR connection are terminated.
l RR release before the normal end of procedure
The location update procedure is terminated.
l RR connection establishment failure (in Iu mode only)
The location update procedure is terminated.

6-7
Handling Suggestions
Based on the cause values carried by the Location Updating Rejected message, you can also
refer to the following suggestions:
l If the reject value is #2, #3, #6, #11, #12, or #13, check that the subscription information
in the HLR and the subscriber data in the VLR are correct.
l If the reject value is #15, check that the CGI and LAC are consistent on the MSC and BSC
sides.
6.3.2 Location Update Failure on the Network Side (Case Study)
This describes the fault, probable causes, and handling suggestions.
Description
Location update fails, and the network sends a Location Updating Reject message.
Analysis
The probable causes are as follows:
l RR connection failure
– If an RR connection fails during a common procedure integrated with the location
update procedure, the behavior of the network is the same as that in a common
procedure.
– If an RR connection fails when a common procedure does not exist, the location update
procedure for the MS is terminated.
l Location update not accepted by the network
If the Location Updating Request message is received with a protocol error, the network
returns a Location Updating Reject message with one of the following reject causes:
– #03 (Illegal MS)
– #97 (Message Type Non-Existent or not Implemented)
– #98 (Message Type not Compatible with the Protocol State)
– #111 (Protocol Error, Unspecified)
Upon sending the response, the network starts the channel release procedure.
l Network failure
If the MSC, VLR, or HLR is faulty, the network sends a Location Updating Reject message
with the cause value #17 (Network Failure).
Generally, if the CGI or LAC on the MSC side is inconsistent with that on the BSC side,
the cause value may also be #17.


So you must check cgi or LAC or BSC under which cell is declared from MSC side and fix it from BSC or MSC side...
Good luck :-)
and do not forget to add reputation for this post ...

to EIAN24, if you don't mind to attach full document related to this solution

I am also inline with adewijaya, only EIAN24 can post the referred document / standard which can help us to understand better...

Hi dears,
all is already posted...the solution is already written.
WRONG LAC or WRONG CGI or wrong BSC ( one in MSC while cell is under another BSC or the cell is locked on MSS side ) or one of this
#03 (Illegal MS)
– #97 (Message Type Non-Existent or not Implemented)
– #98 (Message Type not Compatible with the Protocol State)
– #111 (Protocol Error, Unspecified)


There is no only one solution it depends.
I do not have documentation about this I have only two pages provided me from a colleague of mine traslated from chinese to english and I have already made the cut & copy in the first post.

( still waiting reputation :L )

Dear,
I have one problem that is UE not initiate LA Request. First UE camped on WCDMA network then perform HO to GSM network. During this action UE not sent LA Request message and after one minut later UE send LA Request message to network. This case happened only one BTS. Which case this problem possibe? How to solve this problem. Please help us this issue.