Scribd
Upload
174 views4 pages

Update Device Configuration Data

The document discusses Automatic Device Detection (ADD) capabilities in the Home Location Register - Front End (HLR-FE) system. It provides details on the triggering conditions for sending device configuration data from the HLR-FE to the Device Configuration Register (DCR), including a first detected IMEISV, change in IMEISV, APN changes, IMSI changeover, or subscriber removal. The transfer of data uses a proprietary Ericsson MAP operation and includes fields like IMSI, MSISDN, IMEISV, APNs, and changeover IMSI. Sample decoded records are provided for a removal trigger and other subscriber attribute changes.

Uploaded by

Rafiq Magdy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
174 views4 pages

Update Device Configuration Data

The document discusses Automatic Device Detection (ADD) capabilities in the Home Location Register - Front End (HLR-FE) system. It provides details on the triggering conditions for sending device configuration data from the HLR-FE to the Device Configuration Register (DCR), including a first detected IMEISV, change in IMEISV, APN changes, IMSI changeover, or subscriber removal. The transfer of data uses a proprietary Ericsson MAP operation and includes fields like IMSI, MSISDN, IMEISV, APNs, and changeover IMSI. Sample decoded records are provided for a removal trigger and other subscriber attribute changes.

Uploaded by

Rafiq Magdy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Kindly be informed that ADC triggering is done by trigger initiated from HLR side based on E//

proprietary Update Device Configuration data. Below is more clarification for the ADD feature
on HLR-FE
 
Automatic Device Detection in HLR-FE provides capabilities to store the HLR-FE subscriber's
"International Mobile Equipment Identity - Software Version" (IMEISV) number. This can be
received in the standard parameter 'ADD-info' of Update Location and Update GPRS Location
messages (see figure 8) or in the MAP Update Location message extended with Ericsson private
extension (see figure 9).
HLR-FE also provides capabilities to detect when an end user meets the conditions to trigger
the sending of configuration data and to send the configuration data to the Device
Configuration Register (DCR).
 
The HLR-FE sends configuration data to the DCR “ADC” when one of the following triggering
conditions is met:
         It is the first time an IMEISV is received in HLR for a subscriber.
         The IMEISV received in HLR-FE for a subscriber is different to the IMEISV stored
in the HLR for the subscriber.
         There is a change in the list of APNs (Access Point Name) defined for the
subscriber and the subscriber has an IMEISV stored.
         An IMSI Changeover is executed for a subscriber that has an IMEISV stored.
         A subscriber that has an IMEISV stored is removed.
 
The transference of configuration data from the HLR to the DCR ”ADC” is performed by sending
Ericsson proprietary Update Device Configuration Data MAP V3 operation with the following
data:
         The subscriber's IMSI, to identify such a subscriber.
         The subscriber's Main MSISDN.
         The IMEISV stored in the HLR-FE.
         The list of APNs the subscriber is using in any of his/her PDP-contexts.
         The Changeover IMSI in the case that the Update Device Configuration
         Data operation is triggered as result of an IMSI Changeover.
         In case of subscriber removal an indication of that.
 
 
 
 
The below is the format of MAP UDCD
 
Operation Code = H'F2
Class = 1
 
ASN.1 Formal Description
 
UpdateDeviceConfigurationData  OPERATION ::= {       --Timer m
ARGUMENT                       SEQUENCE {
   imsi                 [0] IMSI                   OPTIONAL,
   msisdn               [1] ISDN-AddressString     OPTIONAL,
   imeisv               [2] IMEISV                 OPTIONAL,
   removeUser           [3] NULL                   OPTIONAL,
   newImsiChangeOver    [4] IMSI                   OPTIONAL,
   apnDataList          [5] APNDataList            OPTIONAL,
   allInformationSent   [6] NULL                   OPTIONAL,
   ...
   multipleSubscription [7] MultipleSubscription   OPTIONAL
   }
 
--"imsi", "msisdn" and "imeisv" parameters are always encoded.
 
RESULT                 SEQUENCE {
        ...}   OPTIONAL
 
ERRORS {
        dataMissing| 
        unexpectedDataValue }
 

Below is sample decoded for the mentioned CDRs


 
1.    Remove subscriber trigger
 

 
2.    Other subscriber attribute changes
 

 
 
 

You might also like