Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2136094.1
Update Date:2017-06-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  2136094.1 :   Location Update Successful In Hlr Even When Vlr Address Is Missing In OCPLMN Template  


Related Items
  • Oracle Communications Subscriber Data Management (SDM)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec SDM
  •  




In this Document
Goal
Solution


Created from <SR 3-11399022731>

Applies to:

Oracle Communications Subscriber Data Management (SDM) - Version SDM 9.1.2 and later
Tekelec

Goal

This document explains why a location update may be successful in Hlr even when the Vlr address is missing in the OCPLMN template.

Solution

Whenever LU request is received from PLMN which is not defined in our HLR,Hlr Checks the default PLMN. A default PLMN is created at system start up. This default PLMN doesn’t have any VLR/GMSC nodes associated to it.

In the case of the ‘Default PLMN’, the Node Range list is empty (N/A), which means that for all Node Ranges the roaming Allowed/Not Allowed verification will be done based on the Allowed IMSI defined for the ‘Default PLMN’ assigned to the subscriber’s OCPLMN Template.

The “Allowed IMSIs list” may:

  1) Be empty (N/A) – this means that the “PLMN is NOT allowed “.Any calls coming from any Node Range defined for that PLMN will be blocked.
  2) Have a list of one or more specific IMSI ranges.This only allows certain subscribers (IMSIs) to make calls from any Node Range defined for that PLMN.
  3) Have a MCC=000 and MNC=000 as IMSI ranges.This allows ALL subscribers (IMSIs) to make calls from any Node Range defined for that PLMN.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback